[issue9968] Let cgi.FieldStorage have named uploaded file

Change by Rhodri James : -- nosy: -Rhodri James ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue9968] Let cgi.FieldStorage have named uploaded file

Change by Rhodri James : -- nosy: +Rhodri James, ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9968] Let cgi.FieldStorage have named uploaded file

Éric Araujo added the comment: I read somewhere that the fact that TemporaryFile does not expose its name is a security feature :/ > On this topic, I was wondering if the changes I propose have any chance of > landing some day in 2.7 land - dunno Python workflow precisely enough. Only bug fix

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: So, this is the patch. -- keywords: +patch Added file: http://bugs.python.org/file22796/fix9968.patch ___ Python tracker ___ _

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: These are the changeset details: changeset: 18337:c2a60de91d2c branch: legacy-trunk user:Guido van Rossum date:Fri Jun 29 13:06:06 2001 + summary: Solve SF bug #231249: cgi.py opens too many (temporary) files. You're right that we might u

[issue9968] Let cgi.FieldStorage have named uploaded file

Éric Araujo added the comment: >>> where does the 1ko barrier come from? Was it only chosen out of >>> performance considerations [...] >> Most certainly. I’ll look at the history of the file later to try to >> find the developer who decided that. > Guido van Rossum made the changes. Before th

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: >> where does the 1ko barrier come from? Was it only chosen out of >> performance considerations [...] > > Most certainly. I’ll look at the history of the file later to try to > find the developer who decided that. Guido van Rossum made the changes. Before that a temp

[issue9968] Let cgi.FieldStorage have named uploaded file

Éric Araujo added the comment: > where does the 1ko barrier come from? Was it only chosen out of > performance considerations [...] Most certainly. I’ll look at the history of the file later to try to find the developer who decided that. > tempfile.NamedTemporaryFile was already used in pyth

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: I got my head in a brown paper bag This is obviously not fixed... except in a locally edited checkout :-( Please be kind to the tired me, forget my last message and don't talk about this to my boss, will you ? It's closing time, really. -- _

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: Oh, my... As we are working with python2.6 on our servers, I overlooked the fact that tempfile.NamedTemporaryFile was already used in python 3 (fixed in r57595, with not many explanations though). Yet, the problem with short length files (cf. msg141179) is still valid

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: Hi, This was test code :-/. It was not under revision control and unfortunately, as I feared then, it turned out I had to stop working shortly after my last message on the low-priority project that made me report this issue . Yet, I have a tarball of a presumably-not-s

[issue9968] Let cgi.FieldStorage have named uploaded file

Éric Araujo added the comment: > Well, this is actually somewhat more complicated than what my first > tests showed due to the way multipart/form-data is dealt with in > FieldStorage.read_multi(). > > The solution I proposed last time only works if the uploaded file is > passed as the first form

[issue9968] Let cgi.FieldStorage have named uploaded file

Changes by Éric Araujo : -- versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: Well, this is actually somewhat more complicated than what my first tests showed due to the way multipart/form-data is dealt with in FieldStorage.read_multi(). The solution I proposed last time only works if the uploaded file is passed as the first form field. I have

[issue9968] Let cgi.FieldStorage have named uploaded file

Éric Araujo added the comment: Thanks for the report. Do you want to work on a patch? -- components: +Library (Lib) -Extension Modules nosy: +eric.araujo, orsenthil stage: -> needs patch versions: +Python 3.2 ___ Python tracker

[issue9968] Let cgi.FieldStorage have named uploaded file

phep added the comment: Oops. I forgot to aknowledge the fact that presently cgi.FieldStorage class documentation (but not the cgi module documentation) tells about the possibility to override the make_file() method in a user subclass to change the present limitation (which is actually how I

[issue9968] Let cgi.FieldStorage have named uploaded file

New submission from phep : Hi, Presently, in cgi.FieldStorage, uploaded file are accessible through a file-like object created by a call to tempfile.TemporaryFile(), probably in order to ensure the file is deleted when the process terminates. The problem is that when one wants to save the dat