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.

classification
Title: base64.decodebytes is only available in Python3.1+
Type: behavior Stage: resolved
Components: Documentation Versions: Python 3.2, Python 3.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, eric.araujo, lurchman, python-dev, r.david.murray, terry.reedy
Priority: normal Keywords:

Created on 2012-08-13 11:47 by lurchman, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg168080 - (view) Author: Andrew Scheller (lurchman) * Date: 2012-08-13 11:47
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
msg168458 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2012-08-17 18:11
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.
msg168460 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2012-08-17 18:28
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.
msg168462 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2012-08-17 18:39
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.
msg168490 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2012-08-18 00:56
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
History
Date User Action Args
2022-04-11 14:57:34adminsetgithub: 59841
2012-08-18 00:56:38r.david.murraysetstatus: open -> closed
resolution: fixed
stage: needs patch -> resolved
2012-08-18 00:56:15python-devsetnosy: + python-dev
messages: + msg168490
2012-08-17 18:39:56r.david.murraysetstatus: closed -> open

type: enhancement -> behavior
versions: + Python 3.2, Python 3.3
nosy: + r.david.murray

messages: + msg168462
resolution: not a bug -> (no value)
stage: resolved -> needs patch
2012-08-17 18:28:08terry.reedysetstatus: pending -> closed
nosy: + terry.reedy
messages: + msg168460

2012-08-17 18:11:44eric.araujosetstatus: open -> pending

versions: - Python 3.1, Python 3.2, Python 3.3, Python 3.4
nosy: + eric.araujo

messages: + msg168458
resolution: not a bug
stage: resolved
2012-08-13 11:47:09lurchmancreate