Actually I did apply that patch and it worked. Problem is, even though
it kept the dev server form simply stopping when I went to upload large
files, it did not speed up the upload process at all.
--~--~-~--~~~---~--~~
You received this message because you are sub
I can't get 2070 to work either. I found
http://code.djangoproject.com/ticket/2613 which fixed up my uploading
problems (at least on the dev server) - have you tried that one?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
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 ar
I have to admit that reading such informative issue reporting and
django experience sharing email is always a pleasure.
It's also interested to know that your path from PHP -> Rails ->
Pylons -> Django. Maybe in another email thread, would like to know
the reason behind your going beyond Pyl
Turns out when I was trying to apply ticket 2070, I was forgetting to
actually enable the upload middleware.
I've enabled it now, but I'm getting errors. This patch *should* fix
the problem if I can get it working.
--~--~-~--~~~---~--~~
You received this message
On 9/14/06, jp <[EMAIL PROTECTED]> wrote:
> It is worth noting that parse_file_upload in django.http uses those
> email and mail libraries a lot. For what I don't know.
Yeah, I just realized that; I didn't poke deeply enough. I'm pretty
certain that's because file uploads (typically) come in as
"
On Sep 14, 2006, at 9:41 PM, jp wrote:
>
> It is worth noting that parse_file_upload in django.http uses those
> email and mail libraries a lot. For what I don't know.
Django uses the email libraries to parse the uploaded content as HTTP
uses MIME encoding for file uploads.
Don
--~--~
It isn't using FileField, infact it isn't touching the DB or using any
kind of manipulator at all. The form consists of a simple box which allows the user to upload a file. The file is
then submitted in a POST request to the second view.
The second view then calls to an outside library which con
On 9/13/06, jp <[EMAIL PROTECTED]> wrote:
> http://paste.e-scribe.com/1564/
> http://paste.e-scribe.com/1565/
It's hard to infer exactly what's going on without knowing more about
the actual code you're using; for example, that first set of profiler
output is spending over 40% of its time in djan
