This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author v+python
Recipients amaury.forgeotdarc, barry, eric.araujo, erob, flox, ggenellina, gvanrossum, oopos, pebbe, pitrou, quentel, r.david.murray, tcourbon, tercero12, tobias, v+python, vstinner
Date 2011-01-10.09:31:52
SpamBayes Score 5.2374406e-07
Marked as misclassified No
Message-id <1294651913.83.0.298873295626.issue4953@psf.upfronthosting.co.za>
In-reply-to
Content
Also, the required behavior of make_file changes, to need the right encoding, or binary, so that needs to be documented as a change for people porting from 2.x. It would be possible, even for files, which will be uploaded as binary, for a user to know the appropriate encoding and, if the file is to be processed rather than saved, supply that encoding for the temporary file.  So the temporary file may not want to be assumed to be binary, even though we want to write binary to it.  So similarly to the input stream, if it is TextIOBase, we want to write to the .buffer.
History
Date User Action Args
2011-01-10 09:31:53v+pythonsetrecipients: + v+python, gvanrossum, barry, amaury.forgeotdarc, ggenellina, pitrou, vstinner, eric.araujo, r.david.murray, oopos, tercero12, tcourbon, tobias, flox, pebbe, quentel, erob
2011-01-10 09:31:53v+pythonsetmessageid: <1294651913.83.0.298873295626.issue4953@psf.upfronthosting.co.za>
2011-01-10 09:31:52v+pythonlinkissue4953 messages
2011-01-10 09:31:52v+pythoncreate