Re: AbstractUser to get more abstract

2013-09-12 Thread Aaron Merriam
Check out django-authtools https://django-authtools.readthedocs.org/en/latest/ Provides a few abstract base classes that make this very easy to accomplish. I'm sure there are other 3rd party apps doing the same. On Thursday, September 12, 2013 2:44:53 PM UTC-6, Abdulaziz Alfoudari wrote: > >

Re: [GSoC] Revamping validation framework and merging django-secure once again

2013-09-12 Thread Kevin Christopher Henry
> > > We probably cannot move checks of `primary_key` and `unique` living in > `FileField.__init__`. We test if one of these two parameters was passed; we > don't check their values. Consider that an user passes unique=False. This > is > the default value, but nevertheless, this should result in

Re: AbstractUser to get more abstract

2013-09-12 Thread Russell Keith-Magee
On Fri, Sep 13, 2013 at 4:44 AM, Abdulaziz Alfoudari < aziz.alfoud...@gmail.com> wrote: > This is a continuation of my post on > stackoverflow > . > > With the introduction of Django 1.5, it was possible to

AbstractUser to get more abstract

2013-09-12 Thread Abdulaziz Alfoudari
This is a continuation of my post on stackoverflow . With the introduction of Django 1.5, it was possible to create a custom User model which is flexible enough to have any user profile the developer wants

Re: Possible breakage of queryset week_day lookup - potential 1.6 release blocker?

2013-09-12 Thread Aymeric Augustin
2013/9/12 Matt Austin > > I've tried the lookups on a new mysql installation (no tzinfo loaded), > and '__month', '__day', and '__week_day' lookups all cause an empty > queryset to be returned. However, '__year' does appear to return the > correct results. > Indeed, year

Re: Possible breakage of queryset week_day lookup - potential 1.6 release blocker?

2013-09-12 Thread Matt Austin
Hi Aymeric, On 12 September 2013 18:16, Aymeric Augustin wrote: > Can you confirm that your project has the USE_TZ setting set to True? Yes, USE_TZ is True, pytz is installed, and default timezone is set to UTC. > I believe I introduced it with a patch that

Re: Allowing custom attributes in Meta classes

2013-09-12 Thread code22
+1 for this. Use case: in one of our projects we had to mark fields allowed for publishing. Using additional meta option would be great for that and I've regretted that it's impossible. W dniu wtorek, 10 września 2013 06:27:29 UTC+2 użytkownik Karan Lyons napisał: > > Hey all, > > I

Re: Support POST of application/json content type

2013-09-12 Thread S Berder
Tom, I get the context and that form is tied to that behavior but outside of "that's how it is now" is there any technical reason for this? I can't read forms code at the moment but will do tonight and will look at how FILES is used in there. I'm not usually afraid by impacts of it's the "right

Re: Support POST of application/json content type

2013-09-12 Thread Tom Christie
> why keep data and files separated Mostly because that's the way it already works, so... * request.data would essentially provide a strict superset of the functionality that request.POST provides. In general you'd be able to replace `request.POST` with `request.data` anywhere and seemlessly

Re: Possible breakage of queryset week_day lookup - potential 1.6 release blocker?

2013-09-12 Thread Aymeric Augustin
Hi Matt, 2013/9/12 Matt Austin > I discovered today that unless timezone data is loaded in to mysql, then > previously working (although functionally broken) week_day lookups return > an empty queryset. > > I couldn't find notes in the docs (release notes or queryset

Possible breakage of queryset week_day lookup - potential 1.6 release blocker?

2013-09-12 Thread Matt Austin
I discovered today that unless timezone data is loaded in to mysql, then previously working (although functionally broken) week_day lookups return an empty queryset. I couldn't find notes in the docs (release notes or queryset week_day docs) that mention this requirement - but happened to read