Message125419
Yeah, the documentation for the email stuff is in the dev docs. There's a short summary in the changes section of the email intro with links to the classes and methods that are affected. But basically you call BinaryFeedParser and feed it a binary data, and everything else works just like it did before, including the fact that get_payload() with no arguments returns a string. If there is non-ASCII data in that string and no charset was specified the binary data will get trashed though. To get the binary data out you call it with decode=True.
I believe you are right that the io module does not support intermixing calls to the main object and its buffer attribute; that's why detach was introduced, I believe. Antoine is nosy on this issue now; he can correct me if I'm wrong.
So unfortunately I think we do need to come at this starting from binary at the beginning and *decoding* as needed (I believe http uses latin-1 when no charset is specified, but I need to double check that). That still leaves the problem of what if anything to do about existing programs that expect every value in a FieldStorage to be a string. Introduce a new method or parameter for getting the binary version of the value, possibly with some flag indicating that parsing detected non-ascii data? |
|
Date |
User |
Action |
Args |
2011-01-05 12:38:16 | r.david.murray | set | recipients:
+ r.david.murray, gvanrossum, barry, amaury.forgeotdarc, ggenellina, pitrou, eric.araujo, v+python, oopos, tercero12, tcourbon, tobias, flox, pebbe, quentel, erob |
2011-01-05 12:38:16 | r.david.murray | set | messageid: <1294231096.27.0.694046761747.issue4953@psf.upfronthosting.co.za> |
2011-01-05 12:38:13 | r.david.murray | link | issue4953 messages |
2011-01-05 12:38:12 | r.david.murray | create | |
|