Message125583
| 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-06.19:46:30 |
| SpamBayes Score | 0.0007875586 |
| Marked as misclassified | No |
| Message-id | <1294343191.98.0.970198841029.issue4953@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
We have several, myself included, that can't use CGI under 3.x because it doesn't take a binary stream. I believe there are several alternatives: 1) Document that CGI needs a binary stream, and expect the user to provide it, either an explicit handle, or by tweaking sys.stdin before calling with a default file stream. 2) Provide a CGI function for tweaking sys.stdin (along with #1) 3) Document that CGI will attempt to convert passed in streams, default or explicit, to binary, if they aren't already, and implement the code to do so. My choice is #3. I see CGI as being used only in HTTP environments, where the data stream should be binary anyway. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-06 19:46:32 | v+python | set | recipients: + v+python, gvanrossum, barry, amaury.forgeotdarc, ggenellina, pitrou, vstinner, eric.araujo, r.david.murray, oopos, tercero12, tcourbon, tobias, flox, pebbe, quentel, erob |
| 2011-01-06 19:46:31 | v+python | set | messageid: <1294343191.98.0.970198841029.issue4953@psf.upfronthosting.co.za> |
| 2011-01-06 19:46:30 | v+python | link | issue4953 messages |
| 2011-01-06 19:46:30 | v+python | create | |