Mailman 3 July 2018 - docs

Another strange expression, 2
by Vrancken, J.L.M. (Jos) 10 Jul '18

10 Jul '18

True == False in (True, False) This expression gives False, whereas in any interpretation, it should be True: (True == False) in (True, False) returns True True == (False in (True, False)) returns True All this in Python 3.7. Is something wrong or am I'm wrong in thinking something's wrong here? Jos Vrancken

2 1

Another strange case
by Vrancken, J.L.M. (Jos) 10 Jul '18

10 Jul '18

True == False in undefinedvariable The expression returns False. Of course the undefinedvariable is indeed undefined. Anything wrong here? Jos Vrancken

1 0

syntax error True == not(False)
by Vrancken, J.L.M. (Jos) 10 Jul '18

10 Jul '18

The expression True == not(False) gives a syntax error. Why is that??? Jos Vrancken

1 0

In an unittest documentation example, __version__ is not PEP 396
by Robert Vanden Eynde 09 Jul '18

09 Jul '18

Hello, in an example in https://docs.python.org/3.8/library/unittest.html#skipping-tests-and-expect… One could read @unittest.skipIf(mylib.__version__ < (1, 3), "not supported in this library version") However, PEP 396 indicates "__version__ number SHOULD be a string", therefore the example is against a good python practice, and package manager like me would loose time googling the what the good practice is. I suggest changing the example to skipIf(mylib.version_info < (1, 3), ...).

1 0

[issue24459] Mention PYTHONFAULTHANDLER in the man page
by Antony Lee 09 Jul '18

09 Jul '18

New submission from Antony Lee: The man page doesn't mention PYTHONFAULTHANDER in the list of environment variables (I haven't thoroughly checked that everyone else is there, either). I would also suggest reordering the environment variables in alphabetical order. ---------- assignee: docs@python components: Documentation messages: 245422 nosy: Antony.Lee, docs@python priority: normal severity: normal status: open title: Mention PYTHONFAULTHANDLER in the man page versions: Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24459> _______________________________________

8 33

[issue34077] doc Be explicit about mock_open created mocks not supporting __iter__
by Andrés Delfino 09 Jul '18

09 Jul '18

New submission from Andrés Delfino <adelfino(a)gmail.com>: I've been bitten by this one, and while the docs are clear in what the created mock objects support, I think something explicit about __iter__ will help. ---------- assignee: docs@python components: Documentation messages: 321327 nosy: adelfino, docs@python priority: normal severity: normal status: open title: doc Be explicit about mock_open created mocks not supporting __iter__ type: enhancement versions: Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34077> _______________________________________

2 3

Hello
by Student 09 Jul '18

09 Jul '18

Hello,I am a Chinese programmer.I want to learn Python,but all of your documentation is in English.Do you have a version of Chinese?If you have,please send me one,Thanks a lot!

1 0

Error in functools.reduce docs
by Dongkyu Choi 08 Jul '18

08 Jul '18

Hi, I report error at the https://docs.python.org/3/library/functools.html#functools.reduce specifically, at “If the optional initializer is present, it is placed before the items of the sequence in the calculation, and [serves as a default when the sequence is empty]. If initializer is not given and sequence contains only one item, the first item is returned. (bracket is added by me for emphasis)” Actually, it should be stated as ‘serves as a default to be run before the lambda reads the given sequence.’ For example, at the code def string_to_int(s): return functools.reduce(lambda running_sum, c: running_sum * 10 + string.digits.index(c), s[s[0] == '-':], 0) * (-1 if s[0] == '-' else 1) t he 0 does the job setting running_sum, c even before it traverses the given string, not restricted to the empty string case. Precisely, if we have s = ' -324 ' , we need to have ru nning_sum=0, c=0 initially, to make it (0*10+index(0)) … as the running_sum cannot be str, if so I get the initializer does the job of setting all the argument of lambda: function as initializer. Please consider this. Thanks. Best regards, Dongkyu Choi +1 (929) 302-9410 creditchoi(a)gmail.com

1 0

[issue34061] Document sqlite3.NotSupportedError exception
by Berker Peksag 08 Jul '18

08 Jul '18

New submission from Berker Peksag <berker.peksag(a)gmail.com>: Most of the exceptions in sqlite3 module were documented in issue 6057 (https://github.com/python/cpython/commit/ed789f9cf9586d94e85115bb516a2ab6b9…) Unfortunately, I noticed that I missed NotSupportedError while reviewing PR 8086. I think it should be documented in the Exceptions section as well: https://docs.python.org/3.8/library/sqlite3.html#exceptions We can adapt the text in PEP 249: https://www.python.org/dev/peps/pep-0249/#notsupportederror ---------- assignee: docs@python components: Documentation keywords: easy messages: 321184 nosy: berker.peksag, docs@python priority: normal severity: normal stage: needs patch status: open title: Document sqlite3.NotSupportedError exception type: enhancement versions: Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34061> _______________________________________

2 8

[issue34051] Update multiprocessing example
by Windson Yang 07 Jul '18

07 Jul '18

New submission from Windson Yang <wiwindson(a)gmail.com>: The docs at https://docs.python.org/3.8/library/multiprocessing.html#synchronization-be… give an example: from multiprocessing import Process, Lock def f(l, i): l.acquire() try: print('hello world', i) finally: l.release() if __name__ == '__main__': lock = Lock() for num in range(10): Process(target=f, args=(lock, num)).start() and point out "For instance one can use a lock to ensure that only one process prints to standard output at a time...". I'm not sure this is a good enough example for the reader. The reader can't tell the difference between the function with l.acquire() or not, The output just shows in the terminal at the same time. So I think a better idea just add time.sleep(0.1) before print('hello world', i) like this: l.acquire() try: # do something here # time.sleep(0.1) print('hello world', i) I can provide a pr if you guys like this idea. ---------- assignee: docs@python components: Documentation messages: 321088 nosy: Windson Yang, docs@python priority: normal severity: normal status: open title: Update multiprocessing example versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34051> _______________________________________

3 7