Re: Problem with custom forms and related objects

On 12/30/06, JMCameron <jmcameron <at> gmail.com> wrote:
>
> Thanks ElGranAzul,  my django code is up to date (via svn), so
> 'oldforms' is equivalent to 'forms' (the __init__.py files are the
> same).   So using 'from django import oldforms as forms' may be better
> form (no pun intended!), but will not fix the problem I'm trying to
> figure out.

True, but seeing oldforms are being phased out in favor of newforms,
problems with the oldforms generally seem to be ignored, except to
suggest that you either wait for newforms, or, if you're up to it,
switch now and help with development by reporting bugs.

I suppose that if you were stuck in an older version, you could work
up your own patch, but seeing you're running the latest trunk, that
seems unlikely.

--

-- 
----
Waylan Limberg
waylan <at> gmail.com

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: What's the best way to learn newforms?

On 12/31/06, Adrian Holovaty <holovaty <at> gmail.com> wrote:
>
> Regarding your deleted comment: Comments on the documentation pages
> are intended to be suggestions and corrections for the docs themselves
> -- not tech support questions. We delete anything that doesn't comment
> directly on the docs, so that the comments section remains helpful.
> The place to ask questions is on django-users, not in the doc
> comments.
>
Is this explained anywhere on the site? Personally, I like this
policy, but I don't recall ever seeing it stated anywhere (except
here). Perhaps a simple link in the comments form to a comments policy
would help avoid this confusion. Just a suggestion.

--

-- 
----
Waylan Limberg
waylan <at> gmail.com

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: rendering multiple dictionaries?

On 12/31/06, Noah Gift <noah.gift <at> gmail.com> wrote:
> Is there an elegant way to avoid nesting dictionaries in render_to_response
> if you have to separate data structures to display...from say another
> function that gets called in your view?  The data structure I am displaying
> is already deeply nested, so I would like to avoid nesting even further if I
> can avoid it.  It makes for a nasty template with too much nesting.
>
You can always subclass Context [1] and do your own thing - passing
that in with the context_instance attribute, but even then, your
custom context must return a dict.

[1]: http://www.djangoproject.com/documentation/templates_python/#subclassing-context-requestcontext

--

-- 
----
Waylan Limberg
waylan <at> gmail.com

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: What's the best way to learn newforms?

On 12/31/06, Waylan Limberg <waylan <at> gmail.com> wrote:
> On 12/31/06, Adrian Holovaty <holovaty <at> gmail.com> wrote:
> >
> > Regarding your deleted comment: Comments on the documentation pages
> > are intended to be suggestions and corrections for the docs themselves
> > -- not tech support questions. We delete anything that doesn't comment
> > directly on the docs, so that the comments section remains helpful.
> > The place to ask questions is on django-users, not in the doc
> > comments.
> >
> Is this explained anywhere on the site? Personally, I like this
> policy, but I don't recall ever seeing it stated anywhere (except
> here). Perhaps a simple link in the comments form to a comments policy
> would help avoid this confusion. Just a suggestion.
>
Bah! I didn't even double check before posting that. I see there
already is a comment. Sorry for the noise.

--

-- 
----
Waylan Limberg
waylan <at> gmail.com

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Curious error

Curious Error

FATAL: sorry, too many clients already

getting the errror
psycopg2.OperationalError at /login
FATAL: sorry, too many clients already
Python     build/bdist.linux-i686/egg/DBUtils/SteadyDB.py in
__init__, line 113

anyone see this

i have DBUtils installed
am using flup
and my postgresql.conf file is this
max_connections = 1024
shared_buffers = 108000

there  are about 103 postgres processes running
of which 99 are idle

any pointers are appreciated

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Is the software behind the Djangobook available?

Just for the record, I would also be very interested in this!
Do you have plans of building into it some way of exporting to other
more format, that might be more manageable for print? (like for
instance docbook or latex)

Cheers,
Filipe

On Dec 28 2006, 9:08 am, "tekNico" <googlegro... <at> tekNico.net> wrote:
> Jacob Kaplan-Moss wrote:
> >> It's not currently available. If I've got time, I might clean it up and
> >> release it... maybe, maybe not.That would be great. 
>
> It would also be nice if the comments system worked with Opera (you
> know, those pesky Nokia 770 handhelds...), but I guess it mainly
> dependes on the YUI library.
>
> -- Nicola Larosa -http://www.tekNico.net/
> In Mac OS X 10.4, Apple deliberately changed Mail.app to use their
> prop- rietary .emlx data format [...]. Now I'm forced to migrate all my
> mail yet again from yet another proprietary format, and the best
> documentation I've found so far is on LiveJournal. Jesus H. Christ,
> somebody deserves to be fired for that.
>  -- Mark Pilgrim, June 2006

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Not all Apps Loaded in Admin Interface?

It looks like there may be some funky problem with imports. The
models.py file imports some external modules that in turn import the
models.py file. Removing the functions that rely on this import and
then removing the import make the admin interface work again, but I
lose a lot of important functions this way. Bleh.

On Dec 30 2006, 2:35 am, "squishywaf... <at> gmail.com"
<squishywaf... <at> gmail.com> wrote:
> On Dec 26, 1:37 pm, "Jeremy Dunck" <jdu... <at> gmail.com> wrote:
>
> > On 12/26/06, squishywaf... <at> gmail.com <squishywaf... <at> gmail.com> wrote:
>
> > > Is there any way to see where this is bombing out? Perhaps some kind of
> > > help from Apache? There are no error messages in the apache2 error log
> > > or on theadmininterface, it's just that the application andallof
> > > its models/classes aren't visible.The app is in INSTALLED_APPS?   The model contains an inner
classAdmin?  The model has at least oneadmin-editable field?
>
> > Code?Yes, the app works just fine outside of the admin interface and the
> admin interface did work for a good while until it suddenly stopped.
> Yes, there is at least one admin-editable field.
>
> If it was a syntax problem, I figured pylint and the Python interpreter
> would pick up on it.

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Not all Apps Loaded in Admin Interface?

As far as code goes, here's the module in question:
http://evennia.googlecode.com/svn/trunk/evennia/trunk/apps/objects/models.py

The Subversion trunk is at:
http://evennia.googlecode.com/svn/trunk/evennia/trunk/

I'm open to ideas!

On Dec 30 2006, 2:35 am, "squishywaf... <at> gmail.com"
<squishywaf... <at> gmail.com> wrote:
> On Dec 26, 1:37 pm, "Jeremy Dunck" <jdu... <at> gmail.com> wrote:
>
> > On 12/26/06, squishywaf... <at> gmail.com <squishywaf... <at> gmail.com> wrote:
>
> > > Is there any way to see where this is bombing out? Perhaps some kind of
> > > help from Apache? There are no error messages in the apache2 error log
> > > or on theadmininterface, it's just that the application andallof
> > > its models/classes aren't visible.The app is in INSTALLED_APPS?   The model contains an inner
classAdmin?  The model has at least oneadmin-editable field?
>
> > Code?Yes, the app works just fine outside of the admin interface and the
> admin interface did work for a good while until it suddenly stopped.
> Yes, there is at least one admin-editable field.
>
> If it was a syntax problem, I figured pylint and the Python interpreter
> would pick up on it.

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---