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 r.david.murray
Recipients bru, docs@python, georg.brandl, planet36, r.david.murray
Date 2014-12-09.15:14:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418138074.52.0.237452082674.issue23017@psf.upfronthosting.co.za>
In-reply-to
Content
This is a bit of a conundrum.  Our (string module) definition of printable is very clear, and it includes the other whitespace characters.

We could document that this does not match the posix definition of printable.  It also does not match the RFC 5822 definition of printable (for example), which does *not* include whitespace characters (not even space), but the posix definition is a more likely source of confusion.

isprintable is a newer function than string.printable, and serves a different purpose.  I suppose that when PEP 3138 was written and implemented the disconnect between the two definitions was not noticed.

For backward compatibility reasons I suspect we are stuck with the discrepancy, but perhaps others will think it worth the pain of changing string.printable.  I kind of doubt it, though.
History
Date User Action Args
2014-12-09 15:14:34r.david.murraysetrecipients: + r.david.murray, georg.brandl, docs@python, planet36, bru
2014-12-09 15:14:34r.david.murraysetmessageid: <1418138074.52.0.237452082674.issue23017@psf.upfronthosting.co.za>
2014-12-09 15:14:34r.david.murraylinkissue23017 messages
2014-12-09 15:14:34r.david.murraycreate