Mailman 3 June 2016 - docs

[issue20699] Document that binary IO classes work with bytes-likes objects
by Serhiy Storchaka 03 Jun '16

03 Jun '16

Serhiy Storchaka added the comment: array is supported explicitly in the Python implementation of readinto(). What if write not "usable with memoryview", but mention memoryview as an example? The object *b* should be a pre-allocated, writable array of bytes, such as :class:`bytearray`, :class:`array.array` or :class:`memoryview`. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20699> _______________________________________

1 0

[issue20699] Document that binary IO classes work with bytes-likes objects
by Martin Panter 03 Jun '16

03 Jun '16

Martin Panter added the comment: Actually this bug report was opened because an implementation that lacked memoryview support was broken by 2.7. The point is to document that (a subset of) memoryview objects may be passed to custom implementations. Does this need a “changed in 2.7” notice? I am not so familiar with the history of Python 2 or the various buffer APIs to be sure. Also see <https://bugs.python.org/issue20699#msg266523>, where I discovered array('b') does not work with io.BytesIO.write(). It seems you have to wrap it in buffer() first, presumably because array() does not support the “new” protocol, but buffer() does. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20699> _______________________________________

1 0

[issue20699] Document that binary IO classes work with bytes-likes objects
by Serhiy Storchaka 03 Jun '16

03 Jun '16

Serhiy Storchaka added the comment: Since the _pyio implementation doesn't support general memoryview-like objects, I consider using the new buffer protocol in the C implementation an implementation detail. Other implementations can lack this support. I think it would be better to left the wording more general ("preallocated writable array of bytes"), but mention other concrete example (array('b'), are there other examples in the stdlib?). ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20699> _______________________________________

1 0

Index "code object" and link to code object definition (issue 15476)
by vadmium+py＠gmail.com 03 Jun '16

03 Jun '16

https://bugs.python.org/review/15476/diff/17455/Doc/library/marshal.rst File Doc/library/marshal.rst (right): https://bugs.python.org/review/15476/diff/17455/Doc/library/marshal.rst#new… Doc/library/marshal.rst:20: object: code I think the “code” index point(s) should be attached to the following paragraph, about support of code and other objects in marshal. This paragraph is about the relationship with the pickle and shelve modules. https://bugs.python.org/review/15476/diff/17455/Doc/library/stdtypes.rst File Doc/library/stdtypes.rst (right): https://bugs.python.org/review/15476/diff/17455/Doc/library/stdtypes.rst#ne… Doc/library/stdtypes.rst:4445: The generated HTML seems to work better if you include the “.. _bltin-code-objects:” label _after_ the index code, instead of before. Otherwise, #bltin-code-objects points to the end of the previous section, rather than into the new section. https://bugs.python.org/review/15476/

1 0

[issue8519] doc: termios and ioctl reference links
by Senthil Kumaran 03 Jun '16

03 Jun '16

Senthil Kumaran added the comment: Thanks Angad and Anatoly for the patches discussions. Thank you Berker for review. Made the changes in all active versions of python. Let this issue reset in peace. ---------- resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8519> _______________________________________

1 0

[issue8519] doc: termios and ioctl reference links
by Roundup Robot 03 Jun '16

03 Jun '16

Roundup Robot added the comment: New changeset 55886a6aed4b by Senthil Kumaran in branch '2.7': [backport to 2.7] - issue8519 - Reference termios and ioctl manual pages in the library documentation. https://hg.python.org/cpython/rev/55886a6aed4b ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8519> _______________________________________

1 0

[issue8519] doc: termios and ioctl reference links
by Roundup Robot 03 Jun '16

03 Jun '16

Roundup Robot added the comment: New changeset f53a0566a290 by Senthil Kumaran in branch '3.5': issue8519 - Reference termios and ioctl manual pages in the library documentation. https://hg.python.org/cpython/rev/f53a0566a290 New changeset 8db146bec24b by Senthil Kumaran in branch 'default': [merge from 3.5] - issue8519 - Reference termios and ioctl manual pages in the library documentation. https://hg.python.org/cpython/rev/8db146bec24b ---------- nosy: +python-dev _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8519> _______________________________________

1 0

[issue20699] Document that binary IO classes work with bytes-likes objects
by Martin Panter 03 Jun '16

03 Jun '16

Martin Panter added the comment: I agree with avoiding the term “bytes-like object” in 2.7. It is easy to be specific when talking about concrete classes like BufferedWriter and BytesIO. But the harder question is what to specify for the abstract base classes. In patch v8, I propose to change the documentation to refer to “sequences of bytes which are usable with ‘memoryview’ ”. Technically, some of the _pyio implementations assume more than this (e.g. len(), iteration and slice assignment), but I have left them alone. ---------- Added file: http://bugs.python.org/file43141/bytes-like-param.py2.v8.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20699> _______________________________________

1 0

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)
by Gregory P. Smith 03 Jun '16

03 Jun '16

Changes by Gregory P. Smith <greg(a)krypto.org>: ---------- resolution: -> fixed stage: needs patch -> commit review status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25931> _______________________________________

1 0

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)
by Roundup Robot 03 Jun '16

03 Jun '16

Roundup Robot added the comment: New changeset a4c0208b10df by Gregory P. Smith in branch '2.7': issue25931: document that socketserver.Forking* are unavailable on platforms https://hg.python.org/cpython/rev/a4c0208b10df ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25931> _______________________________________

1 0