> [snip] > > "Just updated to trunk" doesn't actually tell us what level you are at. I > know there was very recently (within the last couple of hours) a fix made > for a recent bug introduced in upload file handling. I do not not if you > are running with that fix or not. > > So first, make sure you are really at latest, so that you have that fix. > Then, if you are still seeing a problem (since your symptoms don't exactly > match what I've seen of that bug) it would help if you would do a binary > search between the revision you had that worked and the latest, to find out > what changeset, exactly, caused the error. My wild guess would be r10717, > so you might first want to compare r10716 behavior with r10717 as that might > save some time. Or not, if my guess is wrong...this could be due to > something completely different. > > (The behavior where is_valid first causes an AttributeError and subsequently > returns True is because the forms code ensures full_clean on the form is > only called once. Something in full_clean is causing the AttributeError but > it isn't called the 2nd time because the first time through it already > created the _errors dict for the form, which prevents it ever being called > again.) >
Well I went back and tried the 1.0.2 release and that worked. The info I have for the directory is: URL: http://code.djangoproject.com/svn/django/trunk/django Repository Root: http://code.djangoproject.com/svn Repository UUID: bcc190cf-cafb-0310-a4f2-bffc1f526a37 Revision: 10736 Which file or folder are you more interested in? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
