On 27/03/2012, at 9:00 PM, Alex Ogier wrote: > > On Mar 27, 2012 8:45 AM, "Hanne Moa" <[email protected]> wrote: > > > > Let's just do it. Let's not wait for a generic migration tool! I'd > > rather the energy was spent on the app-refactor *now*, and fixing the > > email-fields *now*, which would remove some of the pressure on fixing > > the Identity/Authentication/Authorization architecture. > > > > There's still several months before the 1.5 feature freeze. It's not out of > the realm of possibility that some of these summer projects will land in 1.5. > Given that, I'd rather do it right. > > Proper standards support for the email field is important,
No argument that they're desirable, but as I've pointed out elsewhere -- Django has survived for 6 years with this "fundamentally broken" EmailField default definition. > arguably a 1.5 release blocker, No. There is no argument to be made that this is a release blocker. It will not cause unpredictable data loss, and is not a flaw in a new feature. Those are our criteria for release blockers. In this case, your argument is weakened further by the fact that there is also an easily used workaround (manually specifying max_length). > but so long as there is a good chance that migration support will be 1.5's > poster-child feature then I think email support should be our poster child's > poster child. > There's also a very recent, relatively active thread discussing our options with auth.User, which has a lot of overlap with this change. The wiki discusses all the options, and makes specific mention of the need (and possible migration approaches) for EmailField [1]. Given that these two topics are closely related, I'd rather try and keep the discussions in one place. [1] https://code.djangoproject.com/wiki/ContribAuthImprovements#Parallelconcerns Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
