On Feb 13, 2008 6:50 PM, Michael Newman <[EMAIL PROTECTED]> wrote: > > Thanks for passing that link along. Worse part is that I seriously > managed to almost duplicate that patch verbatim in the last 12 hours. > Shouldn't this be marked as a block to the trunk merge? When I didn't > see it there I thought that I had to have been going crazy. > > This ticket is a duplicate of the error that I got and perhaps should > be removed: http://code.djangoproject.com/ticket/6572 > > Many thanks again, Michael >
Too bad about the duplicated work, but it was probably a learning experience anyway, right? So not entirely useless. Hmm, that ticket (6083) specifies a version of "SVN", therefore it wasn't included in the sweep of marking newforms-admin tickets as either blocking merge or not. Should the migration of auth to newforms be part of the newforms-admin branch? Sure, admin uses auth, but newforms-admin doesn't require that auth use newforms (I've been running on the newforms-admin branch w/ old auth forms fine), and auth is used outside of admin, so it isn't clear to me that migrating auth to newforms is part of the newforms-admin work. But honestly I haven't had time to look into what exactly the problems are that you (and others) have been hitting in this area, so maybe I'm missing some reason why migrating auth to newforms should be done first on newforms-admin instead of just doing it on trunk. As for that other ticket, you could return it yourself as a dup of the one that is still open for the problem. Just fill in some settings here: http://code.djangoproject.com/settings so you don't show up as "Anonymous". Better if it's done by someone who actually has a clue with regard to the problem reported, and that wouldn't be me. Cheers, Karen > On Feb 13, 5:01 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > On Feb 13, 2008 2:57 PM, Michael Newman <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > I hit a little problem last night with registering a new user in the > > > newforms admin branch. I posted my original question on django-users: > > > > >https://groups.google.com/group/django-users/browse_thread/thread/47b. > .. > > > . Working backwards throughout the day, I noticed that > > > django.contrib.auth.forms used old forms. For the life of me I tried > > > to find a patch or request in the trac on this and I couldn't. To > > > quickly get my site up and running I am currently almost complete a > > > new forms.py and changes in views.py that use new forms and solves my > > > mystery error. > > > > > Is there something I am missing? Is there a reason that auth is not > > > ported to new forms yet on the newforms admin? If that reason is time, > > > can I offer this (soon to be complete) port? I just need a little > > > guidance from someone who knows more on why it seems I am the only one > > > to have noticed this. Thanks, > > > > It's been noticed by at least a couple of other people, since there's a > > ticket open for it which references a 2nd that was closed as a dup: > > > > http://code.djangoproject.com/ticket/6083 > > > > I think both tickets have patches as well. Probably no one has yet had > time > > to get this finished up in newforms-admin. Trying out one of the > existing > > patches and providing feedback on it in the ticket would likely be > helpful. > > > > Karen > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
