[issue15636] base64.decodebytes is only available in Python3.1+

Changes by R. David Murray : -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue15636] base64.decodebytes is only available in Python3.1+

Roundup Robot added the comment: New changeset ca5b36754892 by R David Murray in branch '3.2': #15636: add versionadded for decodebytes http://hg.python.org/cpython/rev/ca5b36754892 New changeset a343fa692bb0 by R David Murray in branch 'default': Merge #15636: add versionadded for decodebytes h

[issue15636] base64.decodebytes is only available in Python3.1+

R. David Murray added the comment: We have plenty of "versionadded" and "versionchanged" tags for 3.1 in the docs. We should add one for this as well to the 3.2 and 3.3 docs. -- nosy: +r.david.murray resolution: invalid -> stage: committed/rejected -> needs patch status: closed -> ope

[issue15636] base64.decodebytes is only available in Python3.1+

Terry J. Reedy added the comment: Once a version goes off normal maintenance, we stop patching the manual except for changes related to security fixes. So the 3.1 manual is also frozen (except for possible security fixes). The same is true of 2.6 and will be true of 3.2 when its final maintena

[issue15636] base64.decodebytes is only available in Python3.1+

Éric Araujo added the comment: 3.0 is considered an alpha release by python-dev, is is not officially supported and is basically dead. 3.1 was released very soon after, mostly to fix the slow I/O. That’s why the docs don’t detail what’s new in 3.1, as this version is considered the first Pyt

[issue15636] base64.decodebytes is only available in Python3.1+

New submission from Andrew Scheller: According to the documentation ( http://docs.python.org/py3k/library/base64.html#base64.decodebytes ) both the decodebytes and the deprecated decodestring methods are available in the base64 module in Python3.x However in Python3.0 (I'm testing with version