Re: auth.User: The abstract base class idea

2012-03-21 Thread Alex Ogier
I made a topic branch and refactored everything I thought was nicely reusable from auth.User into abstract models in django/contrib/auth/mixins.py. There are some good reusable pieces inside auth.User, even if you want to entirely scrap Django's notion of identity and the username and/or email fiel

Re: Improved Error Reporting in Django - GSoC

2012-03-21 Thread Andrew Godwin
On 20/03/12 20:33, Sachin Gupta wrote: It seems most of the errors on this page https://code.djangoproject.com/wiki/BetterErrorMessages are very old. It states that if the attribute enctype="multitype/form-data" is not sent then the following error comes up TypeError at ... string indices must b

Re: Schema Alteration API proposal

2012-03-21 Thread Andrew Godwin
On 21/03/12 13:27, Kushagra Sinha wrote: One more thing: The current creation API in django has methods like "sql_create_model" which basically return sql and it is the caller's responsibility to either call cursor.execute on it (syncdb) or output the sql itself (sql). South's (and xtrqt's) desi

Re: Improved Error Reporting in Django - GSoC

2012-03-21 Thread Daniel Sokolowski
FYI: for my development settings I set: TEMPLATE_STRING_IF_INVALID = 'UNDEFINED_VAR: %s' which tells me which variables are undefined. It has some quirks (password reset form in admin link fails or something) but it’s easy to live with during development. From: Sachin Gupta Sent: Tuesday, M

Re: Schema Alteration API proposal

2012-03-21 Thread Kushagra Sinha
One more thing: The current creation API in django has methods like "sql_create_model" which basically return sql and it is the caller's responsibility to either call cursor.execute on it (syncdb) or output the sql itself (sql). South's (and xtrqt's) design is to have functions like "create_table"

Re: Making sure Web APIs built with Django don't have CSRF vulnerabilities.

2012-03-21 Thread Tom Christie
I don't know how much of an issue it really is (or not), but I haven't really seen it being done right. Of all the examples I've found of devs implementing session authentication on top of piston and tastypie, (See here

Re: release blocker in 1.4rc2 ?

2012-03-21 Thread Jannis Leidel
On 21.03.2012, at 04:56, s wrote: > Hi all, > I just opened https://code.djangoproject.com/ticket/17944, not sure it's > should be marked as release-blocker, please could some core-developer check > it ? > > The ticked has 1.4beta1 release, there is no rc2 in the list > I just added 1.4-rc-

Re: auth.User refactor: reboot

2012-03-21 Thread Ian Lewis
Hi, On Tue, Mar 20, 2012 at 10:37 PM, Russell Keith-Magee wrote: > On 20/03/2012, at 8:38 PM, Tom Evans wrote: >> User profiles solve the issue of app specific data in a better way >> than specifying additional fields on a a base user object, >> particularly as the number of apps increases. Whils

Re: auth.User refactor: reboot

2012-03-21 Thread Ian Lewis
Hi, On Tue, Mar 20, 2012 at 2:05 PM, Russell Keith-Magee wrote: > On 20/03/2012, at 8:00 AM, Ian Lewis wrote: >> Though we have had other times where there were multiple types of >> users in a single project. i.e. users that signed up via some >> affiliate program. username is unique so you would

Re: auth.User refactor: reboot

2012-03-21 Thread Alex Ogier
On Wed, Mar 21, 2012 at 2:41 AM, Clay McClure wrote: > > I assume also that most changes would be relatively minor: dropping the > username field, or "fixing" the email field (where the developer gets to > define what that means), but not, say, removing all of the authorization > attributes requir