Mailman 3 September 2019 - docs

[issue30076] Opcode names BUILD_MAP_UNPACK_WITH_CALL and BUILD_TUPLE_UNPACK_WITH_CALL are too long
by Serhiy Storchaka Sept. 3, 2019

Sept. 3, 2019

Serhiy Storchaka <storchaka+cpython(a)gmail.com> added the comment: These opcodes are always used with CALL_FUNCTION_EX (which can be used also without any of them). f(*a, *b, **c, **d) 1 0 LOAD_NAME 0 (f) 2 LOAD_NAME 1 (a) 4 LOAD_NAME 2 (b) 6 BUILD_TUPLE_UNPACK_WITH_CALL 2 8 LOAD_NAME 3 (c) 10 LOAD_NAME 4 (d) 12 BUILD_MAP_UNPACK_WITH_CALL 2 14 CALL_FUNCTION_EX 1 I though about naming CALL_FUNCTION_EX as CALL_FUNCTION_VAR in 3.6, but this name was used in pre-3.6 bytecode with different semantic. Now I think there is smaller change of confusion, so it can be renamed to CALL_FUNCTION_VAR or something other. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue30076> _______________________________________

1 0

[issue30076] Opcode names BUILD_MAP_UNPACK_WITH_CALL and BUILD_TUPLE_UNPACK_WITH_CALL are too long
by Nick Coghlan Sept. 3, 2019

Sept. 3, 2019

Nick Coghlan <ncoghlan(a)gmail.com> added the comment: Reviewing this again now, I think my previous naming suggestion is problematic, as it encourages conflating two different concepts that use similar syntax: * collecting arbitrary positional parameters in a tuple (VAR_POSITIONAL) or arbitrary keyword parameters in a dictionary (VAR_POSITIONAL, VAR_KEYWORD) * unpacking function arguments from iterables (BUILD_VAR_POSITIONAL) or mappings (BUILD_VAR_KEYWORD) I think the fix for that error is straightforward though: replace "VAR" with "ARG" in the new opcode names, giving: * BUILD_ARG_POSITIONAL * BUILD_ARG_KEYWORD That should also read nicely with Zackery's documentation updates. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue30076> _______________________________________

1 0

[issue38004] Duplicated sections in changelog
by Inada Naoki Sept. 3, 2019

Sept. 3, 2019

New submission from Inada Naoki <songofacandy(a)gmail.com>: See TOC in https://docs.python.org/3.7/whatsnew/changelog.html Some releases (*) have multiple "Library" and "Security" sections. (*) e.g. 3.6.0a3, 3.6.0a2, 3.6.0a1, 3.5.3rc1, 3.5.2rc1 ---------- assignee: docs@python components: Documentation messages: 350971 nosy: docs@python, inada.naoki priority: normal severity: normal status: open title: Duplicated sections in changelog versions: Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue38004> _______________________________________

3 3

Import error macOS
by Brent Leeper Sept. 3, 2019

Sept. 3, 2019

Hello, I have been using python3 for several years but have never seen this error. Description: After executing “python3” and starting the cli, I can import the following without error -from cassandra.cluster import Cluster Then I exit and run a .py file whose first line is “from cassandra.cluster import Cluster” which results in the following error. -Traceback (most recent call last): File "cassandra.py", line 1, in <module> from cassandra.cluster import Cluster File "/Users/<user>/Documents/learning/cassandra.py", line 1, in <module> from cassandra.cluster import Cluster ModuleNotFoundError: No module named 'cassandra.cluster'; 'cassandra' is not a package Sure, the import did not work. But the next part is the issue. Now I return back to the cli by executing “python3” and I enter the following (the same as above”) -from cassandra.cluster import Cluster Now I get this error: -Python 3.7.4 (v3.7.4:e09359112e, Jul 8 2019, 14:54:52) [Clang 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from cassandra.cluster import Cluster Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/Users/<user>/Documents/learning/cassandra.py", line 1, in <module> from cassandra.cluster import Cluster ModuleNotFoundError: No module named 'cassandra.cluster'; 'cassandra' is not a package The error is referencing the file but I am not executing it. This is very odd. This continues until I close the terminal instance and open a new one and is reproducible if you take the above steps on my system. If you would like further details, please let me know. Thanks, Brent

1 0

[issue36853] inconsistencies in docs builds (Sphinx 2)
by Jason R. Coombs Sept. 2, 2019

Sept. 2, 2019

New submission from Jason R. Coombs <jaraco(a)jaraco.com>: In working on some docs contributions, I've run into issues where docs builds are failing in CI differently than they're failing locally. Locally, running `make venv` from `Docs/` results in Sphinx 2, whereas on Azure Pipelines, the docs are built with Sphinx 1.8.2 (https://github.com/python/cpython/blob/1d4b16051f8550fd7dada3670a3e83ae13b9…). When running with Sphinx 2, this error emerges when running `make suspicious` when a change is around that triggers suspicious code (such as this commit https://github.com/python/cpython/pull/12547/commits/9bde7faf6f051d4a7306ac…): Exception occurred: File "/Users/jaraco/code/public/cpython/Doc/tools/extensions/suspicious.py", line 154, in report_issue self.warn('[%s:%d] "%s" found in "%-.120s"' % AttributeError: 'CheckSuspiciousMarkupBuilder' object has no attribute 'warn' First, we probably want to make these processes consistent (define the dependencies in exactly one place). Second, we should probably determine why the doc builds are failing on Sphinx 2 and update the `suspicious` code to support Sphinx 2. ---------- assignee: docs@python components: Documentation messages: 341897 nosy: docs@python, jaraco priority: normal severity: normal status: open title: inconsistencies in docs builds (Sphinx 2) type: compile error versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36853> _______________________________________

9 14

[issue38011] xml.dom.pulldom splits text data at buffer size when parsing from file
by Stefan Behnel Sept. 2, 2019

Sept. 2, 2019

Stefan Behnel <stefan_ml(a)behnel.de> added the comment: I don't see anything inherently wrong with having multiple text nodes. In fact, input with very large text content can be considered a security threat (c.f. compression bombs), so a tool like pulldom (which is designed for incremental processing) should not start collecting more content than the user asked for. Getting multiple text nodes in some cases seems an ok-ish price to pay. A documentation PR is welcome. ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python versions: +Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue38011> _______________________________________

1 0

Please help me，How can I download Python3.7.4 Help(.chm) files in Simplified Chinese？
by 杨佳琪 Sept. 2, 2019

Sept. 2, 2019

Hi： I'm a new guy who is learning Python without any programming experience. And I'm learning English at the same time. So it's hard to me for understanding Python3.7.4 Help(.chm) files in English.I tried to search the Internet for a Chinese version,but failed. So,if there is Python3.7.4 Help(.chm) files in Simplified Chinese，Please tell me where I can download it. Best wishes！ watalo form China

1 0

Wrong roman numeral
by Florian Ernst Sept. 2, 2019

Sept. 2, 2019

2 1

Queue module example does not use task_completed on None messages
by Robert C Kahlert Sept. 1, 2019

Sept. 1, 2019

https://docs.python.org/3/library/queue.html#queue-objects (version 3.7.4) That leads to the confusing result that if, after putting the None on the queue, the main thread tries another q.join(), it blocks forever. def worker(): while True: item = q.get() if item is None: q.task_done # <== ADDED break do_work(item) q.task_done() q = queue.Queue()threads = []for i in range(num_worker_threads): t = threading.Thread(target=worker) t.start() threads.append(t) for item in source(): q.put(item) # block until all tasks are doneq.join() # stop workersfor i in range(num_worker_threads): q.put(None)for t in threads: t.join() It might be altogether more natural to write the worker as: def worker(): go_on = True while go_on: item = q.get() if item is None: go_on = False else do_work(item) q.task_done() That makes it clear that all tasks have to be acquitted in order for the queue to be clear on what is going on and when all is finished. Best --rck

1 0

bad example for os.walk
by Harald Dunkel Sept. 1, 2019

Sept. 1, 2019

Hi folks, the first example for os.walk on https://docs.python.org/3/library/os.html doesn't work for broken symbolic links. Should be easy to fix. Regards Harri

1 0