Message273911
| Author |
serhiy.storchaka |
| Recipients |
berker.peksag, legnaleurc, r.david.murray, rhettinger, serhiy.storchaka |
| Date |
2016-08-30.11:36:20 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1472556981.11.0.185073384989.issue27413@psf.upfronthosting.co.za> |
| In-reply-to |
|
| Content |
The last change just sweeps a problem under a rug.
For now json.tool never fails with valid data. But with the --no-ensure-ascii option it can fail when output a string not encodable with the locale encoding. All can work with common cases on common UTF-8 environment, but unexpectedly fail on nonstandard environment. It would be better to output encodable characters as is and represent unencodable characters with \uXXXX encoding. |
|