Chris Jerdonek added the comment:
In the future, now that a few more people know, we could always look to see
what doc changes were made since the last "publication" of the docs (or run the
other `make` commands locally, or ideally, beforehand in cases that warrant
it). The fact that 2.7 published and not the others should have been a tip off
for me.
I wonder if `make patchcheck` could be enhanced to check for unsupported
characters.
Lastly, is there a work-around for the inability to include � in the docs?
That particular difference between u.encode('replace') and
bytes.decode('replace') (? vs. �) seems like an important one to me not to
conflate.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15949>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
