Message106670
| Author |
vstinner |
| Recipients |
benjamin.peterson, flox, georg.brandl, lemburg, loewis, vstinner |
| Date |
2010年05月28日.13:48:54 |
| SpamBayes Score |
0.03981414 |
| Marked as misclassified |
No |
| Message-id |
<1275054536.57.0.357721920168.issue7475@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Explanation the change in Python3 by Guido:
"We are adopting a slightly different approach to codecs: while in Python 2, codecs can accept either Unicode or 8-bits as input and produce either as output, in Py3k, encoding is always a translation from a Unicode (text) string to an array of bytes, and decoding always goes the opposite direction. This means that we had to drop a few codecs that don't fit in this model, for example rot13, base64 and bz2 (those conversions are still supported, just not through the encode/decode API)."
http://www.artima.com/weblogs/viewpost.jsp?thread=208549
--
See also issue #8838. |
|