Mailman 3 November 2015 - docs

Clarify max_length and flush() for zlib decompression (issue 23200)
by vadmium+py＠gmail.com 18 Nov '15

18 Nov '15

Reviewers: , https://bugs.python.org/review/23200/diff/15974/Lib/zipfile.py File Lib/zipfile.py (right): https://bugs.python.org/review/23200/diff/15974/Lib/zipfile.py#newcode922 Lib/zipfile.py:922: not data and Actually I think this condition also needs to fail if any compressed data was passed in: compressed_data = data # Before decompression if ... not compressed_data and not data and ... Please review this at https://bugs.python.org/review/23200/ Affected files: Doc/library/zlib.rst Doc/whatsnew/3.6.rst Lib/encodings/zlib_codec.py Lib/test/test_codecs.py Lib/test/test_zlib.py Lib/zipfile.py Misc/NEWS Modules/zlibmodule.c

1 0

[issue5784] raw deflate format and zlib module
by Martin Panter 18 Nov '15

18 Nov '15

Martin Panter added the comment: Looking at the current zlib module source code, I confirmed that wbits is passed directly to the deflateInit2(windowBits) and inflateInit2(windowBits) parameters. So the following modes could also be added to the documentation for decompression: * Zero: automatically determine size from zlib header * 32 + logarithm: automatically accept either a zlib or gzip header Also, the compressobj() doc string is out of date. It mentions 8–15 but none of the other options. Paul: Perhaps it would be better to say “wbits” corresponds to the format of the stream, rather than mentioning just the window size as currently proposed. Then hopefully the reader would look to see what value is needed for the raw Deflate format. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue5784> _______________________________________

1 0

Re: [docs] raw deflate format and zlib module (issue 5784)
by vadmium+py＠gmail.com 18 Nov '15

18 Nov '15

https://bugs.python.org/review/5784/diff/14652/Doc/library/zlib.rst File Doc/library/zlib.rst (right): https://bugs.python.org/review/5784/diff/14652/Doc/library/zlib.rst#newcode… Doc/library/zlib.rst:84: * -8 to -15: Uses the absolute value of *wbits* as the window size, while absolute value . . . as the logarithm https://bugs.python.org/review/5784/diff/14652/Doc/library/zlib.rst#newcode… Doc/library/zlib.rst:88: the window size, while including a basic :program:`gzip` header as the logarithm https://bugs.python.org/review/5784/diff/14652/Doc/library/zlib.rst#newcode… Doc/library/zlib.rst:143: :func:`compressobj`. When decompressing a stream, *wbits* must not be the history buffer size must not be smaller [According to the zlib inflateInit2() documentation, for the negative case it is the magnitude that cannot be smaller, which makes more sense than the alternative.] https://bugs.python.org/review/5784/

1 0

Re: [docs] generator.throw() documentation inaccurate (issue 14911)
by vadmium+py＠gmail.com 17 Nov '15

17 Nov '15

http://bugs.python.org/review/14911/diff/10905/Doc/reference/expressions.rst File Doc/reference/expressions.rst (right): http://bugs.python.org/review/14911/diff/10905/Doc/reference/expressions.rs… Doc/reference/expressions.rst:446: If provided, the ``tb`` argument is used for the raised exception, otherwise On 2014/02/03 18:37:37, Yury.Selivanov wrote: > ``traceback`` instead of ``tb``? The usual markup for these is actually *traceback* http://bugs.python.org/review/14911/diff/10905/Doc/reference/expressions.rs… Doc/reference/expressions.rst:447: the excepition instance's :attr:`__traceback__` attribute is used. In my experience, if you use the *value* parameter, you have to explicitly give the traceback, otherwise the original traceback gets cleared. http://bugs.python.org/review/14911/diff/10905/Doc/reference/expressions.rs… Doc/reference/expressions.rst:447: the excepition instance's :attr:`__traceback__` attribute is used. exception instance [Spelling] http://bugs.python.org/review/14911/

1 0

[issue24172] Errors in resource.getpagesize module documentation
by Mahmoud Hashemi 17 Nov '15

17 Nov '15

New submission from Mahmoud Hashemi: The resource module's description of resource.getpagesize is woefully misguiding. Reproduced in full for convenience: resource.getpagesize() Returns the number of bytes in a system page. (This need not be the same as the hardware page size.) This function is useful for determining the number of bytes of memory a process is using. The third element of the tuple returned by getrusage() describes memory usage in pages; multiplying by page size produces number of bytes. Besides being vague by not referring to the third element as ru_maxrss, the peak RSS for the process (i.e., not the current memory usage), tests on Linux, Darwin, and FreeBSD show the following: * Linux: ru_maxrss is in kilobytes * Darwin (OS X): ru_maxrss is in bytes * FreeBSD: ru_maxrss is in kilobytes (same as Linux) Knowing the page size is probably useful to someone, but the misinformation has definitely sent more than one person down the wrong path here. Additionally, the correct information should be up in the getrusage() method documentation, closer to relevant field descriptions. Mahmoud ---------- assignee: docs@python components: Documentation messages: 243043 nosy: docs@python, mahmoud priority: normal severity: normal status: open title: Errors in resource.getpagesize module documentation versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24172> _______________________________________

4 4

[issue25615] Document unsorted behaviour of glob.glob
by Dave Jones 17 Nov '15

17 Nov '15

New submission from Dave Jones: As suggested in issue 21748, this is a minor documentation change to make explicitly clear that glob.glob returns unsorted results (on the basis that the existing specification references shell behaviour which is always sorted). ---------- assignee: docs@python components: Documentation files: glob-spec-unsorted.patch keywords: patch messages: 254597 nosy: Dave Jones, docs@python priority: normal severity: normal status: open title: Document unsorted behaviour of glob.glob type: behavior versions: Python 3.6 Added file: http://bugs.python.org/file41029/glob-spec-unsorted.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25615> _______________________________________

4 7

[issue25633] The documentation for urllib.request should mention http.client.HTTPException
by jon orebro 16 Nov '15

16 Nov '15

New submission from jon orebro: The documentation for urllib.request should mention that a robust client using urllib.request must be prepared for exceptions of type http.client.HTTPException in addition to urllib.error.URLError. Example: the server breaks HTTP and returns an empty status line and we get a http.client.BadStatusLine. ---------- assignee: docs@python components: Documentation messages: 254720 nosy: docs@python, jon orebro priority: normal severity: normal status: open title: The documentation for urllib.request should mention http.client.HTTPException type: behavior versions: Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25633> _______________________________________

2 1

[issue13821] misleading return from isidentifier
by Raymond Hettinger 16 Nov '15

16 Nov '15

Changes by Raymond Hettinger <raymond.hettinger(a)gmail.com>: ---------- nosy: +pitrou _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13821> _______________________________________

1 0

[issue13821] misleading return from isidentifier
by Serhiy Storchaka 16 Nov '15

16 Nov '15

Changes by Serhiy Storchaka <storchaka(a)gmail.com>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python, haypo, serhiy.storchaka stage: -> needs patch type: -> behavior versions: +Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13821> _______________________________________

1 0

[issue16394] Reducing tee() memory footprint
by Raymond Hettinger 15 Nov '15

15 Nov '15

Raymond Hettinger added the comment: Unlike the other "equivalents" in the docs, this one is further away from the actual implementation. So, I think I should add a clarification that the example code is a "rough logical equivalent" but that actual implementation may have shared queues (Jython, PyPy, and IronPython are free to have their own implementation choices). ---------- priority: normal -> low _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16394> _______________________________________

1 0