Hi!
It's looking reasonably good indeed but not ready to be merged into trunk
right now. It has some problems with django models and regression tests.
I've merge it with Django revision tagged as 1.2.3 some times ago (look here
for more details
https://github.com/alekam/django/commits/app-loading-
Wonderful, thanks a lot for the answer :)
cheers,
Thomas
On Thu, Jan 20, 2011 at 12:07 AM, Gabriel Hurley wrote:
> If you try this in any of the more recent versions (sorry I don't know
> exactly when this was changed) you'll get a ViewDoesNotExist exception
> telling you which view in which modu
For good or bad, in Django a BooleanField is only ever supposed to be True
or False.
A default of False seems the logical equivalent to the default of '' on a
not-null CharField.
If you want a nullable boolean, you should use the separate
NullBooleanField.
--
You received this message because
I've been reading django/db/models/fields/files.py to figure out how
FileFields work under the hood, and I've noticed a bit I don't
understand. The __getstate__ method of FieldFile does:
return {'name': self.name, 'closed': False, '_committed': True,
'_file': None}
but the closed attribute of Fie
Maybe have a management command for manage.py that could do this validation
along with any other sanity checks that may be worthwhile.
Doing validation automatically on startup, especially if only done with
development server or when DEBUG is True would only serve to hide subtle
issues with laz
On Thu, Jan 20, 2011 at 4:52 PM, Chris Beaven wrote:
> For good or bad, in Django a BooleanField is only ever supposed to be True
> or False.
> A default of False seems the logical equivalent to the default of '' on a
> not-null CharField.
>
> If you want a nullable boolean, you should use the se
Hola,
on the users list, David Walker bought up a discussion on Localisation
that I was able to help him with. His follow up was detailed (settings
precedence and en_GB date formats) and well beyond my ability to
answer correctly.
The thread is here:
http://groups.google.com/group/django-users/b
