[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 3.0.1 built from source) the base64 module only has the decodestring method, it doesn't have decodebytes. IMHO the documentation should be updated to reflect this. It looks like decodebytes was added to Python3.1 by http://bugs.python.org/issue3613 ---------- assignee: docs@python components: Documentation messages: 168080 nosy: docs@python, lurchman priority: normal severity: normal status: open title: base64.decodebytes is only available in Python3.1+ type: enhancement versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue15636> _______________________________________
É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 Python 3 version. If this explanation satisfies you, I will close this bug. Thanks for the report anyway. ---------- nosy: +eric.araujo resolution: -> invalid stage: -> committed/rejected status: open -> pending versions: -Python 3.1, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue15636> _______________________________________
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 maintenance release comes out. Andrew, we recommend that you ignore 3.0 even if you are trying to write multi-version 3.x code. ---------- nosy: +terry.reedy status: pending -> closed _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue15636> _______________________________________
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 -> open type: enhancement -> behavior versions: +Python 3.2, Python 3.3 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue15636> _______________________________________
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 http://hg.python.org/cpython/rev/a343fa692bb0 ---------- nosy: +python-dev _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue15636> _______________________________________
Changes by R. David Murray <rdmurray@bitdance.com>: ---------- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue15636> _______________________________________
participants (5)
-
Andrew Scheller -
R. David Murray
-
Roundup Robot
-
Terry J. Reedy
-
Éric Araujo