Message170993
| Author |
ezio.melotti |
| Recipients |
chris.jerdonek, docs@python, ezio.melotti, georg.brandl, loewis, ned.deily, python-dev |
| Date |
2012年09月22日.13:18:09 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1348319890.32.0.768750922323.issue15949@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I usually get the result of the cronjob via email if there's a failure;
Maybe it should go to python-committers or some other public ML, so that other devs can see and possibly fix the issue.
> I wonder if `make patchcheck` could be enhanced to check
> for unsupported characters.
That sounds like a good idea to me.
> Lastly, is there a work-around for the inability to include �
> in the docs?
'\ufffdabc' is acceptable, and it is what non-utf-8 terminals print.
> That particular difference between u.encode('replace') and
> bytes.decode('replace') (? vs. �) seems like an important
> one to me not to conflate.
Indeed I was confusing the two. I'm not actually even sure that the Unicode standard mandates these specific replacement characters (IIRC there's even a way to configure them), and I was under the impression that '?' was sometimes used during the decoding, but after a few tests it seems I was wrong. |
|