Mailman 3 January 2019 - docs

[issue32603] Deprecation warning on strings used in re module
by Cheryl Sabella Jan. 20, 2019

Jan. 20, 2019

New submission from Cheryl Sabella <chekat2(a)gmail.com>: I apologize if this is a duplicate question, but I couldn't find another issue about this. It's hard to search on 're'. In 3.7, I get a deprecation warning when using a regular string with re escape characters: >>> s = '123abcd' >>> re.findall('\d', s) <stdin>:1: DeprecationWarning: invalid escape sequence \d ['1', '2', '3'] Of course, this works: >>> s = '123abcd' >>> re.findall(r'\d', s) ['1', '2', '3'] I know that the documentation strongly suggests using raw strings with re, but I didn't see anywhere mentioning that it would be a requirement. I would think this would break a lot of 're' code. ---------- assignee: docs@python components: Documentation messages: 310300 nosy: csabella, docs@python priority: normal severity: normal status: open title: Deprecation warning on strings used in re module type: enhancement versions: Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue32603> _______________________________________

4 6

[issue35789] Typo in unittest.mock docs
by Jim Carroll Jan. 20, 2019

Jan. 20, 2019

New submission from Jim Carroll <jim(a)carroll.com>: There is a typo in the unittest.mock documentation found at https://docs.python.org/3/library/unittest.mock.html. There are seven(7) instances of the word assret, where the author clearly intended assert. ---------- assignee: docs@python components: Documentation messages: 334087 nosy: docs@python, jamercee priority: normal severity: normal status: open title: Typo in unittest.mock docs type: enhancement versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35789> _______________________________________

1 1

3. An Informal Introduction to Python
by C Velson Horie Jan. 19, 2019

Jan. 19, 2019

I am just starting to learn Python. I miscoded the block, because I did not understand the formatting conventions. As a result the Fibonacci series was 0,0,0.. and I could not stop it except by closing the command window. I tried cntl-X, Esc etc - nothing worked. How do I stop a process in Python? -- Velson Horie

1 0

[issue13322] buffered read() and write() does not raise BlockingIOError
by Martin Panter Jan. 19, 2019

Jan. 19, 2019

Martin Panter <vadmium+py(a)gmail.com> added the comment: Issue 35762 was opened specifically about Izbyshev’s case: TextIOWrapper behaviour with a non-blocking file. Calling “os.fdopen” with mode='r' (text mode) returns a TextIOWrapper object. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue13322> _______________________________________

1 0

[issue33995] test_min_max_version in test_ssl.py fails when Python is built against LibreSSL; {min,max}imum_version behavior differs from OpenSSL
by Alan Huang Jan. 18, 2019

Jan. 18, 2019

New submission from Alan Huang <Alan.Huang(a)utdallas.edu>: LibreSSL's implementation of the function used to get the minimum and maximum SSL versions supported differs from OpenSSL's. In short, the issue is in the implementations of `SSL_CTX_new` - OpenSSL initializes variables `ret->{min,max}_proto_version` to 0, while LibreSSL initializes corresponding variables to those of the `SSL_METHOD` given. As such, when Python is built with LibreSSL, the default values for an instance of ssl.SSLContext are, in the case of ssl.SSLContext(), ctx.minimum_version = <TLSVersion.TLSv1: 769>; ctx.maximum_version = <TLSVersion.TLSv1_2: 771>. This is NOT what test_ssl.py expects; it expects OpenSSL's behavior of initializing the version variables to zero, which _ssl.c then translates to PY_PROTO_{MIN,MAX}IMUM_SUPPORTED -> ssl.TLSVersion.{MIN,MAX}IMUM_SUPPORTED. Additionally, LibreSSL, when `SSL_CTX_set_{min,max}_proto_version` is called with `version` equal to zero, explicitly sets the minimum / maximum values equal to the minimum / maximum values for the `SSL_METHOD` it was called with (namely, 769/770/771, in the case of `TLS_method()`), not the minimum / maximum values supported by the library. I have sent an email to the LibreSSL mailing list asking for clarification on this point, namely, if this is intended behavior. If it is, there are two ways that come to mind to work around this behavior. Both ways would only be necessary if `IS_LIBRESSL`. 1. Skip `test_min_max_version`. 2. Instead of testing that ctx is equal *to* the extremes after it's been set to one of the extremes, test that it's equal to the actual constants. There are two ways this could be accomplished as well: a. Use PY_PROTO_{MIN,MAX}IMUM_AVAILABLE, defined in _ssl.c (this may require the addition of another call to `PyModule_AddIntConstant` to provide access to the constant from _ssl). The downside to this approach is that it assumes that `TLS_method()`, or whatever `SSL_METHOD` test_ssl.py uses has lower and upper bounds equal to PY_PROTO_{MIN,MAX}IMUM_AVAILABLE, which may not always be the case. b. Access and store the values for ctx.{min,max}imum_value on creation, then reference them after setting. Either of these approaches would likely also have the benefit of removing the need for `self.assertIn(ctx.minimum_version, {ssl.TLSVersion.TLSv1_2, ssl.TLSVersion.TLSv1_3})`. The test that failed was: ====================================================================== FAIL: test_min_max_version (test.test_ssl.ContextTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/alan/src/cpython/Lib/test/test_ssl.py", line 1066, in test_min_max_version ctx.minimum_version, ssl.TLSVersion.MINIMUM_SUPPORTED AssertionError: <TLSVersion.TLSv1: 769> != <TLSVersion.MINIMUM_SUPPORTED: -2> Addendum: I found the documentation for ssl.TLSVersion.{MAX,MIN}IMUM_SUPPORTED confusing at first - it took me quite a while to realize what the purpose of the constants were; I would have expected them to contain the maximum and minimum protocol versions supported by the library; I see why it was phrased that way, after having boned up on ssl.py, _ssl.c, and OpenSSL/LibreSSL, but think it could could be made clearer. ---------- assignee: docs@python components: Documentation, SSL, Tests messages: 320703 nosy: Alan.Huang, alex, christian.heimes, docs@python, dstufft, janssen priority: normal severity: normal status: open title: test_min_max_version in test_ssl.py fails when Python is built against LibreSSL; {min,max}imum_version behavior differs from OpenSSL type: behavior versions: Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue33995> _______________________________________

2 4

[issue23156] Update tix install information in tkinter tix chapter of doc
by Terry J. Reedy Jan. 17, 2019

Jan. 17, 2019

New submission from Terry J. Reedy: Update tix install info in doc. "Using tix" starts with 3 lines for testing one's tix install and continues '''If this fails, you have a Tk installation problem which must be resolved before proceeding. Use the environment variable TIX_LIBRARY to point to the installed Tix library directory, and make sure you have the dynamic object library (tix8183.dll or libtix8183.so) in the same directory that contains your Tk dynamic object library (tk8183.dll or libtk8183.so). The directory with the dynamic object library should also have a file called pkgIndex.tcl (case sensitive), which contains the line: package ifneeded Tix 8.1 [list load "[file join $dir tix8183.dll]" Tix]''' Almost nothing above matches my working-with-tix 3.4.2 Win 7 install. I do have a tix library directory: python34/tcl/tix8.4.3, but the version number is much newer. Since it is in the right place, TIX_LIBRARY is not needed and there is none. python34/DLLs contains tcl86t.dll and tk86t.dll and NO tix####.dll. Is the once separate tix dll now part of tk dll? I cannot find pkgIndex.tcl; it is certainly not in the DLLs directory nor in the /tcl. The current doc seems useless to people who do not have tix working. See, for example, https://stackoverflow.com/questions/27751923/tix-widgets-installation-issue which is a semi-repeat question and which claims seeing similar reports elsewhere on the net. ---------- assignee: docs@python components: Documentation, Tkinter messages: 233368 nosy: docs@python, serhiy.storchaka, terry.reedy, zach.ware priority: normal severity: normal stage: needs patch status: open title: Update tix install information in tkinter tix chapter of doc type: behavior versions: Python 2.7, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23156> _______________________________________

5 13

[issue34161] Tutorial 7.1 str.format() code example syntax error
by Orlando Jan. 17, 2019

Jan. 17, 2019

New submission from Orlando <oboffill(a)icloud.com>: Tutorial 7.1 str.format() example (https://docs.python.org/3.7/tutorial/inputoutput.html#fancier-output-format…): [1]yes_votes = 42_572_654 ; no_votes = 43_132_495 [2]percentage = (yes_votes/(yes_votes+no_votes) [3]'{:-9} YES votes {:2.2%}'.format(yes_votes, percentage)) Proposed Fix: Remove first open parens on line 2 and last close parens on line 3. ---------- assignee: docs@python components: Documentation messages: 321977 nosy: docs@python, oboff priority: normal severity: normal status: open title: Tutorial 7.1 str.format() code example syntax error versions: Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34161> _______________________________________

6 24

PDF-Files only available in Letter-Format
by Heinrich Ottinger Jan. 17, 2019

Jan. 17, 2019

*Dear Mr. van Rossum, * *dear members of the great Python-Team! * I want to thank you for your job and what you make available for the public! Please let my say, that there seams to be a little mistake in the PDF-Files you offered for download this night: In the ZIP-File " https://docs.python.org/3.7/archives/python-3.7.2-docs-pdf-a4.zip" there are PDF-Files in the Letter-Format as well - instead of A4-Format! With kind regards from Tübingen in Southern Germany, *Heinrich Ottinger*

1 0

[issue35744] Problem in the documentation of numpy.random.randint in python 2.7
by Jay Jan. 15, 2019

Jan. 15, 2019

New submission from Jay <jay.pokarna10(a)gmail.com>: Official Documentation of python 2.7 mentions that numpy.random.randint(a,b) will return a random integer from N such that a<=N<=b. But I have run the code and I have found that it never returns equal to b. So, what I did was I ran numpy.random.randint(0,1) for 50 milion times and finally printed the sum. The output was 0. I don't know if this a documentation or an implementation issue, but this is an issue which needs to be looked at. I am attaching the code that I ran. ---------- assignee: docs@python components: Documentation files: sample.py messages: 333701 nosy: Jay, docs@python priority: normal severity: normal status: open title: Problem in the documentation of numpy.random.randint in python 2.7 type: behavior versions: Python 2.7 Added file: https://bugs.python.org/file48051/sample.py _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35744> _______________________________________

2 1

[issue35738] Update timeit documentation to reflect default repeat of three
by Jayanth Raman Jan. 15, 2019

Jan. 15, 2019

New submission from Jayanth Raman <raman.jayanth(a)gmail.com>: In the Examples section of the timeit documentation, repeat() returns a list of size three. But the default is now five and the documentation should reflect that. Thanks. ---------- assignee: docs@python components: Documentation messages: 333635 nosy: docs@python, jayanth priority: normal severity: normal status: open title: Update timeit documentation to reflect default repeat of three type: enhancement versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35738> _______________________________________

5 10