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 ncoghlan
Recipients ncoghlan
Date 2014-06-16.11:36:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402918605.38.0.604956966245.issue21777@psf.upfronthosting.co.za>
In-reply-to
Content
There are currently no dedicated docs for the bytes and bytearray methods - the relevant section just refers back to the str methods. This isn't sufficient, since the str methods cover of lot of stuff related to Unicode that isn't relevant to the binary sequence types, and it doesn't cleanly cover the differences either (like the fact that several methods accept integers).

I've started work on a patch that documents the binary APIs explicitly, although bytes and bytearray still share docs. The methods are grouped into three categories:

- work with arbitrary binary data
- assume ASCII compatibility by default, but can still be used with arbitrary binary data when given suitable arguments
- can only be used safely with data in an ASCII compatible format

I've worked through and updated the new entries for the first category, but the latter two categories are still just copy-and-paste from the str docs.
History
Date User Action Args
2014-06-16 11:36:46ncoghlansetrecipients: + ncoghlan
2014-06-16 11:36:45ncoghlansetmessageid: <1402918605.38.0.604956966245.issue21777@psf.upfronthosting.co.za>
2014-06-16 11:36:45ncoghlanlinkissue21777 messages
2014-06-16 11:36:44ncoghlancreate