Message112165
| Author |
flox |
| Recipients |
effbot, flox, georg.brandl, gvanrossum, lemburg, r.david.murray, scoder |
| Date |
2010年07月31日.16:55:39 |
| SpamBayes Score |
0.033125773 |
| Marked as misclassified |
No |
| Message-id |
<1280595345.62.0.0463089960626.issue8047@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Patch updated here, and on Rietveld too.
http://codereview.appspot.com/664043
Rules (as discussed):
- tree.tostring(encoding=None) => encodes to "US-ASCII"
(compatible with 2.7 and lxml.etree)
- tree.tostring(encoding="unicode") => outputs Unicode
- tree.tostring(encoding=str) => outputs Unicode
(compatible with lxml.etree)
For 2.7, no change planned.
For 3.1, do we keep the current behavior?
- tree.tostring(encoding=None) => outputs Unicode |
|