Message176547
| Author |
vstinner |
| Recipients |
asvetlov, berker.peksag, docs@python, ezio.melotti, python-dev, serhiy.storchaka, vstinner |
| Date |
2012年11月28日.15:00:05 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAMpsgwaSScO+TWOrit20SJQ_i86zeM03Z+LKDNtNskDS+5T7Sw@mail.gmail.com> |
| In-reply-to |
<1354106250.75.0.290416956392.issue16323@psf.upfronthosting.co.za> |
| Content |
"If a byte sequence can be decoded as a surrogate character and
*errors* is not ``"strict"``, then the byte sequence is escaped using
the ``"surrogateescape"`` error handler instead of being decoded."
I don't understand this sentence but it sounds to be wrong. The
"surrogateescape" is only used if errors="surrogateescape"...
If errors is set and is different to "strict" and "surrogateescape",
an error is raised.
2012年11月28日 Andrew Svetlov <report@bugs.python.org>:
>
> Andrew Svetlov added the comment:
>
> Really I don't know what's better. Victor, what do you think?
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue16323>
> _______________________________________ |
|