Continued research (I kept asking people) suggests that this is a consequence of moving from Python2.4 to Python2.5. The options appear to be:
* Downgrade Python to 2.4 * Find a "more compatible" copy method. I'd really rather not downgrade Python, but I don't know how to find a "more compatible" copy method. (My web searches so far have been fruitless, because the keywords are too common.) Can anyone point me in the right direction? Thanks, pjm On Mar 19, 2:05 pm, pjmorse <flashesofpa...@gmail.com> wrote: > In my application's admin console, there's a tiny form for updating > the image associated with a specific model. > > When a file is uploaded, the application reaches this code: > > if request.method == 'POST': > file = request.FILES.copy() > > ...and fails with this error: > > object.__new__(cStringIO.StringO) is not safe, use > cStringIO.StringO.__new__() > > The stack tracehttp://dpaste.com/hold/173776/shows me that the > actual error is happening at a lower level than my actual call, and > some browsing around the archives for this list tells me that (a) this > isn't an uncommon problem, and (b) "deepcopy" seems to be the root of > my problem. > > (For those who don't click through to the traceback, this is Django > 1.0.2 final, Python 2.5.1. The traceback is from my development > version.) > > How can I grab the uploaded file for future manipulation which working > around "deepcopy"? > > Thanks, > > pjm -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
