This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author chris.jerdonek
Recipients chris.jerdonek, docs@python, ezio.melotti, georg.brandl, loewis, ned.deily, python-dev
Date 2012-09-22.12:54:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348318464.79.0.384519736744.issue15949@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012-09-22 12:54:25chris.jerdoneksetrecipients: + chris.jerdonek, loewis, georg.brandl, ned.deily, ezio.melotti, docs@python, python-dev
2012-09-22 12:54:24chris.jerdoneksetmessageid: <1348318464.79.0.384519736744.issue15949@psf.upfronthosting.co.za>
2012-09-22 12:54:24chris.jerdoneklinkissue15949 messages
2012-09-22 12:54:23chris.jerdonekcreate