Mailman 3 December 2015 - docs

Re: [docs] Wrong references to deprecated find_module instead of find_spec (issue 23936)
by takowl＠gmail.com 04 Dec '15

04 Dec '15

http://bugs.python.org/review/23936/diff/16097/Doc/glossary.rst File Doc/glossary.rst (right): http://bugs.python.org/review/23936/diff/16097/Doc/glossary.rst#newcode312 Doc/glossary.rst:312: implement at least one of the methods :meth:`find_spec`, On 2015/12/04 00:51:30, vadmium wrote: > Which find_spec()? MetaPathFinder.find_spec() or PathEntryFinder.find_spec(). Or > is the assumed signature such that the differences do not matter? That depends on which kind of finder it is. My understanding is that as of Python 3.3, 'finder' is a rather abstract notion that encompasses the two distinct kinds. Maybe 'finder' should be removed from the glossary entirely, and other parts of the docs should be explicit about which type of finder they want. But if there is anywhere appropriate to describe the more abstract notion of a 'finder', it's probably in the glossary. http://bugs.python.org/review/23936/diff/16097/Doc/library/sys.rst File Doc/library/sys.rst (right): http://bugs.python.org/review/23936/diff/16097/Doc/library/sys.rst#newcode7… Doc/library/sys.rst:782: A list of :term:`meta path finder` objects that have their :meth:`find_spec` On 2015/12/04 00:51:30, vadmium wrote: > :meth:`~importlib.abc.MetaPathFinder.find_spec`; also twice below Done. http://bugs.python.org/review/23936/

1 0

Reporting Bugs
by 韩俊刚 04 Dec '15

04 Dec '15

21.12.3. Examples>>> data == b'' Truemay be:print(data ==b'') url : https://docs.python.org/3.4/library/http.client.html#httpresponse-objects

1 0

Reporting Bugs
by 韩俊刚 04 Dec '15

04 Dec '15

21.12.3. Examples >>> data == b'' True may be: print(data ==b'') url : https://docs.python.org/3.4/library/http.client.html#httpresponse-objects

1 0

[issue23220] Documents input/output effects of how IDLE runs user code
by irdb 04 Dec '15

04 Dec '15

Changes by irdb <electro.nnn(a)gmail.com>: ---------- nosy: +irdb _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23220> _______________________________________

1 0

Re: [docs] Wrong references to deprecated find_module instead of find_spec (issue 23936)
by vadmium+py＠gmail.com 03 Dec '15

03 Dec '15

https://bugs.python.org/review/23936/diff/16097/Doc/glossary.rst File Doc/glossary.rst (right): https://bugs.python.org/review/23936/diff/16097/Doc/glossary.rst#newcode312 Doc/glossary.rst:312: implement at least one of the methods :meth:`find_spec`, Which find_spec()? MetaPathFinder.find_spec() or PathEntryFinder.find_spec(). Or is the assumed signature such that the differences do not matter? https://bugs.python.org/review/23936/diff/16097/Doc/glossary.rst#newcode313 Doc/glossary.rst:313: :meth:`find_loader` or :meth:`find_module`. Perhaps linking to :meth:`~importlib.abc.PathEntryFinder.find_loader` and :meth:`~importlib.abc.Finder.find_module` would be appropriate here? https://bugs.python.org/review/23936/diff/16097/Doc/library/sys.rst File Doc/library/sys.rst (right): https://bugs.python.org/review/23936/diff/16097/Doc/library/sys.rst#newcode… Doc/library/sys.rst:782: A list of :term:`meta path finder` objects that have their :meth:`find_spec` :meth:`~importlib.abc.MetaPathFinder.find_spec`; also twice below https://bugs.python.org/review/23936/

1 0

[issue15068] fileinput requires two EOF when reading stdin
by Serhiy Storchaka 03 Dec '15

03 Dec '15

Changes by Serhiy Storchaka <storchaka(a)gmail.com>: ---------- versions: +Python 2.7 Added file: http://bugs.python.org/file41226/fileinput_no_buffer-2.7.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15068> _______________________________________

1 0

[issue15068] fileinput requires two EOF when reading stdin
by Serhiy Storchaka 03 Dec '15

03 Dec '15

Changes by Serhiy Storchaka <storchaka(a)gmail.com>: Added file: http://bugs.python.org/file41225/fileinput_no_buffer.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15068> _______________________________________

1 0

[issue15068] fileinput requires two EOF when reading stdin
by Serhiy Storchaka 03 Dec '15

03 Dec '15

Changes by Serhiy Storchaka <storchaka(a)gmail.com>: Removed file: http://bugs.python.org/file41224/fileinput_no_buffer.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15068> _______________________________________

1 0

[issue15068] fileinput requires two EOF when reading stdin
by Serhiy Storchaka 03 Dec '15

03 Dec '15

Changes by Serhiy Storchaka <storchaka(a)gmail.com>: ---------- nosy: +gvanrossum _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15068> _______________________________________

1 0

[issue15068] fileinput requires two EOF when reading stdin
by Serhiy Storchaka 03 Dec '15

03 Dec '15

Serhiy Storchaka added the comment: Using readlines() instead of readline() was added in 4dbbf322a9df for performance. But it looks that now this is not needed. Naive implementation with readline() is about 2 times slower, but with careful optimization we can achieve the same performance (or better). Here are results of benchmarks. Unpatched: $ mkdir testdir $ for i in `seq 10`; do for j in `seq 1000`; do echo "$j"; done >"testdir/file$i"; done $ ./python -m timeit -s "import fileinput, glob; files = glob.glob('testdir/*')" -- "f = fileinput.input(files)" "while f.readline(): pass" 10 loops, best of 3: 56.4 msec per loop $ ./python -m timeit -s "import fileinput, glob; files = glob.glob('testdir/*')" -- "list(fileinput.input(files))"10 loops, best of 3: 68.4 msec per loop Patched: $ ./python -m timeit -s "import fileinput, glob; files = glob.glob('testdir/*')" -- "f = fileinput.input(files)" "while f.readline(): pass" 10 loops, best of 3: 47.4 msec per loop $ ./python -m timeit -s "import fileinput, glob; files = glob.glob('testdir/*')" -- "list(fileinput.input(files))" 10 loops, best of 3: 63.1 msec per loop The patch also fixes original issue. It also fixes yet one issue. Currently lines are buffered and you need to enter many lines first then get first line: >>> import fileinput >>> fi = fileinput.input() >>> line = fi.readline() qwerty asdfgh zxcvbn ^D >>> line 'qwerty\n' With the patch you get the line just as it entered. ---------- assignee: docs@python -> serhiy.storchaka stage: needs patch -> patch review versions: +Python 3.4, Python 3.5, Python 3.6 -Python 2.7, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file41224/fileinput_no_buffer.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15068> _______________________________________

1 0