Mailman 3 November 2018 - docs

[issue35109] Doctest in CI uses python binary built from master causing DeprecationWarnings
by Karthikeyan Singaravelan Nov. 3, 2018

Nov. 3, 2018

New submission from Karthikeyan Singaravelan <tir.karthi(a)gmail.com>: Currently we run doctest in CI and we use the environment variable PYTHON to get the path of python binary to be used for virtualenv creation. We set PYTHON=../python in .travis.yml at [0] before running tests thus this causes the CI to use development version of the binary. Some of the modules used for doctest have incompatible changes related to importing from collections. The DeprecationWarning related code will be removed in 3.8 thus it will cause the doctest to fail while using the modules in CI. Since I have enabled -W in issue34081 they are visible now. I propose using stable version of Python like python 3.7 so that when we remove collections import related code in master the doctest doesn't fail on Travis. There are respective PRs for this warnings in the repo but using stable version will fix this. We don't need to test the modules against the master branch of Python for doctest which is currently doing. Sample warning : https://travis-ci.org/python/cpython/jobs/448195459#L2603 > /home/travis/build/python/cpython/Doc/venv/lib/python3.8/site-packages/babel/localedata.py:17: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working > from collections import MutableMapping On local machine the .travis.yml is not executed thus it uses PYTHON=python3 in Doc/Makefile and thus this not a problem locally building the docs that uses a stable version of Python. Adding @mdk for feedback on this. [0] https://github.com/python/cpython/blob/master/.travis.yml#L164 ---------- assignee: docs@python components: Build, Documentation messages: 328886 nosy: docs@python, mdk, xtreak priority: normal severity: normal status: open title: Doctest in CI uses python binary built from master causing DeprecationWarnings versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35109> _______________________________________

3 8

[issue35032] Remove the videos from faq/Windows
by Stéphane Wirtel Nov. 3, 2018

Nov. 3, 2018

New submission from Stéphane Wirtel <stephane(a)wirtel.be>: In the FAQ of Windows, there are two references to external videos for the configuration of a dev environment for Windows, but these videos are no longer available because the domain name no longer exists. ---------- assignee: docs@python components: Documentation, Windows messages: 328139 nosy: docs@python, matrixise, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Remove the videos from faq/Windows versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35032> _______________________________________

2 9

[issue32666] Valgrind documentation seems to need updating
by Reuben Thomas Nov. 3, 2018

Nov. 3, 2018

New submission from Reuben Thomas <rrt(a)sc3d.org>: I have just been trying to use Valgrind (in my case, to debug code in a library being tested via a Cython module). It is working fine, but there seem to be some discrepancies between the documentation in README.valgrind and valgrind-python.supp on the one hand, and the actual code on the other. README.Valgrind says (current git master): Second, you must do one of the following: * Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c, then rebuild Python * Uncomment the lines in Misc/valgrind-python.supp that suppress the warnings for PyObject_Free and PyObject_Realloc However, Objects/objmalloc.c no longer contain this symbol (though Python/dtoa.c does). Further, in https://bugs.python.org/issue31494 I find the following comment: Also, I don't think --with-pydebug works well with valgrind. It's either: 1) --with-pydebug 2) CFLAGS="-O0 -g" --with-valgrind 3) CFLAGS="-O0 -g" --without-pymalloc Combining 2) and 3) probably does not hurt, but is not necessary. It would be useful to have this information in README.valgrind. Also, the provided suppressions do not currently work with a normal build of Python, at least with Python 2.7 (with the PyObject_{Free,Realloc} suppressions uncommented). There seem to be at least two problems: 1. Extra symbols from LTO. This can be fixed by adding "*" to PyObject_Realloc in all its suppressions. 2. After fixing that, I still get one more "Invalid read of size 4": ==3227== Invalid read of size 4 ==3227== at 0x4FCEE2: long_dealloc.lto_priv.323 (abstract.c:2000) ==3227== by 0x4BA22B: frame_dealloc (frameobject.c:458) ==3227== by 0x4BA22B: PyEval_EvalCodeEx (ceval.c:3593) ==3227== by 0x4C16E6: fast_function (ceval.c:4445) ==3227== by 0x4C16E6: call_function (ceval.c:4370) I can't see how this is related to any existing suppression. I am using the stock Python 2.7 on Ubuntu 16.04. I find that I can work around both the above problems (that is, use the suppressions file as-is, just uncommenting the extra suppressions for PyObject_{Free,Realloc}) by using Ubuntu's debug build of Python (installed as /usr/bin/python-dbg). It is built with --with-pydebug. Finally, README.valgrind says: "Valgrind is used periodically by Python developers to try to ensure there are no memory leaks or invalid memory reads/writes." Another reason to use Valgrind is, as in my case, to debug unrelated C code that is being run via Python (this is often a convenient way to write tests). I suggest deleting this sentence and making it more obvious how to simply make Python "transparent to Valgrind" for those trying to debug C libraries. To summarise: i. It seems that for current Python 3, this text: * Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c, then rebuild Python needs to be updated. ii. For Python 2.7 at least, and possibly Python 3, extra suppressions are needed to use a standard build. iii. It would be good to have the specific build advice from https://bugs.python.org/issue31494 in README.valgrind. iv. It would be nice to clarify how to use a normal build of Python (e.g. by splitting the advice into "For Python developers" and "For Python users"). Given some guidance on what is correct, and what is desired/acceptable, I'd be happy to work up a patch to README.valgrind and valgrind-python.supp. ---------- assignee: docs@python components: Documentation messages: 310673 nosy: docs@python, rrt priority: normal severity: normal status: open title: Valgrind documentation seems to need updating versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue32666> _______________________________________

4 4

[issue35150] Misc/README.valgrind out-of-date
by Robert Henry Nov. 2, 2018

Nov. 2, 2018

New submission from Robert Henry <rrh.henry(a)gmail.com>: File Misc/README.valgrind is out of date with respect to python3.8. There are important sections of this file that are 15 years old! Example: the README.valgrind refers to "Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c" but there's no such symbol in obmalloc.c (There is in Python/dtoa.c) I have no idea if the valgrind suppression file Misc/valgrind-python.supp is up to date, but it bears examination by an expert. ---------- assignee: docs@python components: Documentation messages: 329151 nosy: docs@python, rrh priority: normal severity: normal status: open title: Misc/README.valgrind out-of-date versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35150> _______________________________________

2 1

[issue29341] Missing accepting path-like object in docstrings of os module functions
by Pablo Galindo Salgado Nov. 2, 2018

Nov. 2, 2018

Pablo Galindo Salgado <pablogsal(a)gmail.com> added the comment: The docstrings are fixed and the (manual!) backports to 3.7 and 3.6 are done. Very good job, Luna! ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue29341> _______________________________________

1 0

[issue29341] Missing accepting path-like object in docstrings of os module functions
by Pablo Galindo Salgado Nov. 2, 2018

Nov. 2, 2018

Change by Pablo Galindo Salgado <pablogsal(a)gmail.com>: ---------- Removed message: https://bugs.python.org/msg329149 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue29341> _______________________________________

1 0

[issue29341] Missing accepting path-like object in docstrings of os module functions
by Pablo Galindo Salgado Nov. 2, 2018

Nov. 2, 2018

Pablo Galindo Salgado <pablogsal(a)gmail.com> added the comment: The docstrings are fixed and the m(anual!) backports to 3.7 and 3.6 are done. Very good job, Luna! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue29341> _______________________________________

1 0

[issue29341] Missing accepting path-like object in docstrings of os module functions
by Pablo Galindo Salgado Nov. 2, 2018

Nov. 2, 2018

Pablo Galindo Salgado <pablogsal(a)gmail.com> added the comment: New changeset 08026b103ea8f4c9f2b5045ef7806dd8b760da2b by Pablo Galindo (BNMetrics) in branch '3.7': [3.7]bpo-29341: Backport b942707 3.7 (#10298) https://github.com/python/cpython/commit/08026b103ea8f4c9f2b5045ef7806dd8b7… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue29341> _______________________________________

1 0

[issue29341] Missing accepting path-like object in docstrings of os module functions
by Pablo Galindo Salgado Nov. 2, 2018

Nov. 2, 2018

Pablo Galindo Salgado <pablogsal(a)gmail.com> added the comment: New changeset 8d2f88fb17468642813108977bb9ec5f7a065b84 by Pablo Galindo (BNMetrics) in branch '3.6': [3.6]bpo-29341: Backport b942707 3.6 (GH-10299) https://github.com/python/cpython/commit/8d2f88fb17468642813108977bb9ec5f7a… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue29341> _______________________________________

1 0

[issue29341] Missing accepting path-like object in docstrings of os module functions
by Luna Chen Nov. 2, 2018

Nov. 2, 2018

Change by Luna Chen <luna(a)bnmetrics.com>: ---------- pull_requests: +9608 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue29341> _______________________________________

1 0