Re: deprecation of AUTH_PROFILE_MODULE

2011-05-01 Thread Karen Tracey
On Sun, May 1, 2011 at 12:39 PM, Mikhail Korobov wrote: > Hi folks, > > what do you think about deprecating AUTH_PROFILE_MODULE and .get_profile() > or removing the suggestion to use it from the docs in 1.4 release? > There are broader issues with extending User model but

deprecation of AUTH_PROFILE_MODULE

2011-05-01 Thread Mikhail Korobov
Hi folks, what do you think about deprecating AUTH_PROFILE_MODULE and .get_profile() or removing the suggestion to use it from the docs in 1.4 release? There are broader issues with extending User model but I think this one can be handled separately. Some links: *

countries model or list like settings.LANGUAGES

2011-05-01 Thread Mateusz Harasymczuk
I have to agree with this guy: http://code.djangoproject.com/ticket/5446 There should be a model to hold country name and language: {% quote %} The idea is to have something like: country = models.CountryField() language = models.LanguageField() Instead of: lang = models.CharField (

Fwd: Re : Validate that IntegerField is a valid Signed value

2011-05-01 Thread Cal Leeming [Simplicity Media Ltd]
Done [Django] #15939 : SignedIntegerField? / UnsignedIntegerField? as part of the core fields.py [Django] #15940

Re: Re : Validate that IntegerField is a valid Signed value

2011-05-01 Thread Mathieu AGOPIAN
I really can't tell if those two new fields would be integrated in core, either wait for feedback here, and/or give it a try with a ticket (and i'm pretty sure it'll land in "Design Decision Needed"). On May 1, 2:42 pm, "Cal Leeming [Simplicity Media Ltd]"

Re : Validate that IntegerField is a valid Signed value

2011-05-01 Thread Cal Leeming [Simplicity Media Ltd]
Yeah, subclassing sounds the way forward. I was thinking something like: SignedIntegerField = IntegerField(min_value=–2147483648, max_value= 2147483647) UnsignedIntegerField = IntegerField(min_value=0, max_value=4294967295) Do you think there would be much chance in having these two field types

Re: Re : Validate that IntegerField is a valid Signed value

2011-05-01 Thread Mathieu AGOPIAN
For reference, this discussion is linked to http://groups.google.com/group/django-developers/browse_thread/thread/f0b8ddbda03a2d8e and to the ticket http://code.djangoproject.com/ticket/15923 Cal, The only thing that i could imagine regarding "fixing" this issue would indeed be a documentation