I never could get #2070 to work, and Django's file upload mechanism is really iffy currently. What I ended up doing was this:
--- I found out a solution to the problem! Today I thought about possibly subverting Django's way of parsing file uploads and using something else to do so, while still using Django itself for everything else. After a question in IRC about it, someone mentioned that request.POST and request.FILES are evaluated in a 'lazy' fashion; the form isn't actually parsed until either of those are explicity referenced in your code. With this in mind, I figured I could use the code from Pylons that does form parsing. This part of Pylons is actually done using a portion of Paste, paste.request.parse_formvars. http://pythonpaste.org/module-paste.request.html#parse_formvars Using this, I was able to simply say: 'from paste.request import parse_formvars' And then in the view itself: input = parse_formvars(request.environ) to be more consistent with Django, I believe I couldn't done something like: request.POST = parse_formvars(request.environ) Basically this just bypassed Django's handling of the form and used Paste instead. I'm happy to say that was literally the only change I had to make in my code. Of course I didn't say request.FILES['upload'].filename, but input['upload'].filename did it all for me. Even better news is...this version is actually *faster* than the Pylons version. Only by a second or less, but it is faster. Everything works fine. I'd like to suggest a few things: 1. Ticket 2070 needs to be looked at. Currently it incorporates both an AJAXY upload progress indicator AND a fix on the upload system. These two items should not be bundled; one is drastically more important than the other 2. I honestly can't even say that Ticket 2070 would've fixed my problem, it might. But it my be a good idea to include paste.request.parse_formvars as a 'light' and efficient way of parsing file uploads. It is licensed under an MIT license, there would be no problem including it, but it might be very important if Ticket 2070 isn't a fix to the problem I was having. Hope to hear back from someone, and thanks for those that helped me out along the way. --- More on my problem, situation, and solution: http://groups.google.com/group/django-developers/browse_thread/thread/c5705e1d800c1579/29ee07234f1a0f8c?lnk=gst&q=problems+with+the+way&rnum=1#29ee07234f1a0f8c --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
