Message126233
| Author | v+python |
|---|---|
| Recipients | amaury.forgeotdarc, andyharrington, barry, eric.araujo, erob, flox, georg.brandl, ggenellina, grahamd, oopos, pebbe, pitrou, quentel, r.david.murray, tcourbon, tobias, v+python, vstinner |
| Date | 2011-01-14.06:17:37 |
| SpamBayes Score | 8.8832724e-07 |
| Marked as misclassified | No |
| Message-id | <1294985861.32.0.846726240977.issue4953@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Graham, Thanks for your comments. Fortunately, if the new charset parameter is not supplied, no mucking with stdout or stderr is done, which is the only reason I cannot argue strongly against the feature, which I would have implemented as a separate API... it doesn't get in the way if you don't use it. I would be happy to see the argv code removed, but it has been there longer than I have been a Python user, so I just live with it ... and don't pass arguments to my CGI scripts anyway. I've assumed that is some sort of a debug feature, but I also saw some code in the HTTPCGIServer and http.server that apparently, on some platforms, actually do pass parameters to CGI on the command lines. I would be happy to see that code removed too, but it also predates my Python experience. And no signs of "if debug:" by either of them! |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-14 06:17:41 | v+python | set | recipients: + v+python, barry, georg.brandl, amaury.forgeotdarc, ggenellina, pitrou, vstinner, andyharrington, eric.araujo, grahamd, r.david.murray, oopos, tcourbon, tobias, flox, pebbe, quentel, erob |
| 2011-01-14 06:17:41 | v+python | set | messageid: <1294985861.32.0.846726240977.issue4953@psf.upfronthosting.co.za> |
| 2011-01-14 06:17:38 | v+python | link | issue4953 messages |
| 2011-01-14 06:17:37 | v+python | create | |