[issue22635] subprocess.getstatusoutput changed behavior in 3.4 (maybe 3.3.4?)

Gregory P. Smith added the comment: New changeset 2eb0cb4787d02d995a9bb6dc075983792c12835c by Gregory P. Smith in branch 'master': bpo-22635: Update the getstatusoutput docstring. (#3435) https://github.com/python/cpython/commit/2eb0cb4787d02d995a9bb6dc075983792c12835c -- ___

[issue31330] argparse.RawTextHelpFormatter does not maintain lines separated by more than one newline

Changes by R. David Murray : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list ma

[issue31036] building the python docs requires the blurb module

Changes by Ned Deily : -- pull_requests: +3437 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue22635] subprocess.getstatusoutput changed behavior in 3.4 (maybe 3.3.4?)

Gregory P. Smith added the comment: New changeset fb4c28c032e26b3cdbe67eae3769d45207ac3507 by Gregory P. Smith (Miss Islington (bot)) in branch '3.6': [3.6] bpo-22635: Update the getstatusoutput docstring. (GH-3435) (#3439) https://github.com/python/cpython/commit/fb4c28c032e26b3cdbe67eae3769d4

[issue28958] Python should return comperhansive error when SSLContext cannot be created

Christian Heimes added the comment: New changeset 611a3eab194dfd0a54e541e8e8547051df24bcfc by Christian Heimes in branch '2.7': [2.7] bpo-28958: Improve SSLContext error reporting. (GH-3414) (#3433) https://github.com/python/cpython/commit/611a3eab194dfd0a54e541e8e8547051df24bcfc --

[issue28958] Python should return comperhansive error when SSLContext cannot be created

Christian Heimes added the comment: New changeset 6c99b652f7909f86753b9e567ea18c95ee736e83 by Christian Heimes in branch '3.6': [3.6] bpo-28958: Improve SSLContext error reporting. (GH-3414) (#3432) https://github.com/python/cpython/commit/6c99b652f7909f86753b9e567ea18c95ee736e83 --

[issue28958] Python should return comperhansive error when SSLContext cannot be created

Changes by Christian Heimes : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue20854] multiprocessing.managers.Server: problem with returning proxy of registered object

Davin Potts added the comment: It appears that the multiple workarounds proposed by the OP (@allista) address the original request and that there is no bug or unintended behavior arising from multiprocessing itself. Combined with the lack of activity in this discussion, I'm inclined to believ

[issue27340] bytes-like objects with socket.sendall(), SSL, and http.client

Christian Heimes added the comment: New changeset 9423f5d68874ff2e500cbe072c25f883cf754be8 by Christian Heimes in branch '3.6': [3.6] bpo-27340: Use memoryview in SSLSocket.sendall() (GH-3384) (#3434) https://github.com/python/cpython/commit/9423f5d68874ff2e500cbe072c25f883cf754be8 --

[issue27340] bytes-like objects with socket.sendall(), SSL, and http.client

Christian Heimes added the comment: In Python 3.6 and master, SSLSocket.sendall() now accepts any bytes-like object that can be cast to bytes. Since it uses a sliced memoryview instead of sliced bytes, it avoids extra copies of the payload, too. -- resolution: -> fixed stage: patch re

[issue29136] Add OP_NO_TLSv1_3

Christian Heimes added the comment: PR 1363 also introduced ssl.HAS_TLSv1_3 flag for unit tests. The flag is required because OpenSSL 1.1.1-dev can be compiled without TLS 1.3 support. The development version always defines OP_NO_TLSv1_3 to a non-zero value. Further more the PR adds a test for

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Nick Coghlan added the comment: New changeset 5a8516701f5140c8c989c40e261a4f4e20e8af86 by Nick Coghlan in branch 'master': bpo-31344: Per-frame control of trace events (GH-3417) https://github.com/python/cpython/commit/5a8516701f5140c8c989c40e261a4f4e20e8af86 -- _

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Changes by Nick Coghlan : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue31036] building the python docs requires the blurb module

Ned Deily added the comment: New changeset 590665c399fc4aa3c4a9f8e7104d43a02e9f3a0c by Ned Deily in branch 'master': bpo-31036: Allow sphinx and blurb to be found automatically (#3440) https://github.com/python/cpython/commit/590665c399fc4aa3c4a9f8e7104d43a02e9f3a0c -- __

[issue31036] building the python docs requires the blurb module

Changes by Roundup Robot : -- pull_requests: +3438 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue31390] pydoc.Helper.keywords missing async and await

New submission from Robert Weiner: Shouldn't async and await be added to the pydoc keywords list? -- assignee: docs@python components: Documentation messages: 301657 nosy: docs@python, rsw priority: normal severity: normal status: open title: pydoc.Helper.keywords missing async and await

[issue31390] pydoc.Helper.keywords missing async and await

Changes by Robert Weiner : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue31036] building the python docs requires the blurb module

Ned Deily added the comment: New changeset 645c1e421348790d49eab863279a41cb2b6a007a by Ned Deily (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31036: Allow sphinx and blurb to be found automatically (GH-3440) (#3441) https://github.com/python/cpython/commit/645c1e421348790d49eab863279a41cb

[issue30450] Pull Windows dependencies from GitHub rather than svn.python.org

Changes by Zachary Ware : -- keywords: +patch pull_requests: +3439 stage: backport needed -> patch review ___ Python tracker ___ ___

[issue31036] building the python docs requires the blurb module

Ned Deily added the comment: For the 3.6 and master branches, I've now enhanced Doc/Makefile to better find its tools. If the doc venv is present, e.g. make venv was run, the Doc build recipe will use sphinx-build and blurb from there, otherwise the process PATH will be search for installed v

[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds

Nathaniel Smith added the comment: Should I open a new issue for the __aexit__ part of this issue then, or...? The reason neither asyncio nor trio use the approach you describe is that it makes it impossible to break out of infinite loops, and trio in particular has entirely solved this proble

[issue29136] Add OP_NO_TLSv1_3

Christian Heimes added the comment: New changeset cb5b68abdeb1b1d56c581d5b4d647018703d61e3 by Christian Heimes in branch 'master': bpo-29136: Add TLS 1.3 cipher suites and OP_NO_TLSv1_3 (#1363) https://github.com/python/cpython/commit/cb5b68abdeb1b1d56c581d5b4d647018703d61e3 -- _

[issue31387] asyncio should make it easy to enable cooperative SIGINT handling

Nick Coghlan added the comment: Issue 31388 is also potentially relevant here, as registering a signal handler for SIGINT isn't sufficient to cover all potential cases were Py_AddPendingCall gets called. In particular, the tests for issue 29988 use Py_AddPendingCall to emulate Ctrl-C, rather t

[issue30640] NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx()

STINNER Victor added the comment: New changeset f032e9237aa7d43d21e0b04d685c36bddf7078c1 by Victor Stinner (Zackery Spytz) in branch '3.6': [3.6] bpo-30640: Fix undefined behavior in _PyFunction_FastCallDict() and PyEval_EvalCodeEx() (GH-2919) (#2964) https://github.com/python/cpython/commit/f

[issue30640] NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx()

STINNER Victor added the comment: It's now fixed in Python 3.6 and master (3.7). FYI this issue was also detected by Coverity as CID 1415964. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue31388] Provide a way to defer SIGINT handling in the current thread

Nathaniel Smith added the comment: Note also that adding a check to ceval is not sufficient -- there are also lots of calls to PyErr_CheckSignals scattered around the tree, e.g. next to every syscall that can return EINTR. I've considered proposing something like this in the past, since it fee

[issue31379] run_profile_task in Makefile should add $(RUNSHARED)

Xiang Zhang added the comment: New changeset 7dcea4c8769e4f12197646922f399a699c3e2a5a by Xiang Zhang in branch '2.7': bpo-31379: Added $(RUNSHARED) to run_profile_task (#3422) https://github.com/python/cpython/commit/7dcea4c8769e4f12197646922f399a699c3e2a5a -- ___

[issue31379] run_profile_task in Makefile should add $(RUNSHARED)

Changes by Xiang Zhang : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___ Py

[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds

Nick Coghlan added the comment: A new issue (depending on this one and potentially on issue 31388) would be helpful, especially if you were able to use the testing trace hook from this PR to reproduce the problem. The reason I've taken the async with change out of this issue is because it's u

[issue29136] Add OP_NO_TLSv1_3

Changes by Christian Heimes : -- keywords: +patch pull_requests: +3440 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds

Nick Coghlan added the comment: Nathaniel, actually, I think issue 31387 is the right one to comment on, as still being able to interrupt long-running loops in synchronous code is a quality of implementation concern for that RFE. -- ___ Python track

[issue29572] Upgrade installers to OpenSSL 1.0.2k

Changes by STINNER Victor : -- pull_requests: +3441 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue29136] Add OP_NO_TLSv1_3

Changes by Christian Heimes : -- pull_requests: +3442 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue31387] asyncio should make it easy to enable cooperative SIGINT handling

Nick Coghlan added the comment: As per Nathaniel's comments on issue 29988 and 31388, doing this robustly relies on: 1. the event loop being able to reliably guard itself and __aexit__ method implementations against interrupts (issue 31388) 2. "async with" statements ensuring that if the frame

[issue29572] Upgrade installers to OpenSSL 1.0.2k

Changes by STINNER Victor : -- pull_requests: +3443 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue26465] Upgrade OpenSSL shipped with python installers

Changes by STINNER Victor : -- pull_requests: +3445 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue26930] Upgrade installers to OpenSSL 1.0.2h

Changes by STINNER Victor : -- pull_requests: +3446 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue26268] Update python.org installers to use OpenSSL 1.0.2f

Changes by STINNER Victor : -- pull_requests: +3444 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue28248] Upgrade installers to OpenSSL 1.0.2j

Changes by STINNER Victor : -- pull_requests: +3447 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue27354] SSLContext.load_verify_locations cannot handle paths on Windows which cannot be encoded using mbcs

Christian Heimes added the comment: 3.6 uses PyUnicode_FSConverter() to convert the cafile and capath arguments, then passes PyBytes_AS_STRING() to OpenSSL. What needs to change to support non-ASCII chars on Windows? -- assignee: christian.heimes -> steve.dower versions: -Python 3.5

[issue31391] Forward-port test_xpickle from 2.7 to 3.x

New submission from Zachary Ware: Python 2.x has a test called test_xpickle which confirms that pickles can be successfully passed back and forth between different versions of Python. This should be forward-ported to 3.x, and include tests between the python under test, 3.6, 3.5, 3.4, and 2.7

[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds

Nathaniel Smith added the comment: On another topic: you should add a test where the 'with' block exits by raising an exception, because in this case the interpreter jumps straight to WITH_CLEANUP_START, potentially skipping the DEFER_PENDING_UNTIL entirely. -- ___

[issue31392] Upgrade installers to OpenSSL 1.1.0f

Changes by Steve Dower : -- keywords: +patch pull_requests: +3448 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue31392] Upgrade installers to OpenSSL 1.1.0f

New submission from Steve Dower: As per usual -- assignee: christian.heimes components: SSL, Windows, macOS messages: 301673 nosy: christian.heimes, ned.deily, paul.moore, ronaldoussoren, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Upgrade in

[issue29136] Add OP_NO_TLSv1_3

Christian Heimes added the comment: New changeset 9f2b3d4c2899f9caea2e47063061a76e460ac618 by Christian Heimes in branch '3.6': [3.6] bpo-29136: Add TLS 1.3 cipher suites and OP_NO_TLSv1_3 (GH-1363) (#3444) https://github.com/python/cpython/commit/9f2b3d4c2899f9caea2e47063061a76e460ac618

[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds

Nick Coghlan added the comment: In addition to adding a test case to ensure exceptions were handled correctly, I also added test cases for return, break, and continue, and all four new tests initially failed. Adding a special case for WITH_CLEANUP_START resolved those, but the tests need an a

[issue30389] distutils._msvccompiler cannot find VS 2017

STINNER Victor added the comment: I'm pretty sure that the commit 05f01d85257d0f3409c7335aaf0bf6a6da7eecb7 introduced this memory leak: test_distutils leaked [8736, 8740, 8740] references, sum=26216 test_distutils leaked [8640, 8642, 8642] memory blocks, sum=25924 http://buildbot.python.org/al

[issue2771] Test issue

Ezio Melotti added the comment: test -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue29136] Add OP_NO_TLSv1_3

Christian Heimes added the comment: New changeset b9a860f3bf80b0d4a6c25d0f2f6ef849d9bf3594 by Christian Heimes in branch '2.7': [2.7] bpo-29136: Add TLS 1.3 cipher suites and OP_NO_TLSv1_3 (GH-1363) (#3446) https://github.com/python/cpython/commit/b9a860f3bf80b0d4a6c25d0f2f6ef849d9bf3594

[issue30860] Consolidate stateful C globals under a single struct.

Eric Snow added the comment: New changeset 2ebc5ce42a8a9e047e790aefbf9a94811569b2b6 by Eric Snow in branch 'master': bpo-30860: Consolidate stateful runtime globals. (#3397) https://github.com/python/cpython/commit/2ebc5ce42a8a9e047e790aefbf9a94811569b2b6 -- _

[issue31393] Fix the use of PyUnicode_READY()

New submission from Serhiy Storchaka: PyUnicode_READY() raises an exception when returns -1 (MemoryError or ValueError). Not all code that calls PyUnicode_READY() handles this property. The following PR fixes all uses of PyUnicode_READY(). * If PyUnicode_READY() returns -1 the caller should ei

[issue31393] Fix the use of PyUnicode_READY()

Changes by Serhiy Storchaka : -- keywords: +patch pull_requests: +3449 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue26904] Difflib quick_ratio() could use Counter()

Michael Cuthbert added the comment: I've tried to get the system to not be slower on small sets by not creating a Counter for less than 60 items, and managed to get within 10% of the speed for small sequences while maintaining the 3-3.6x speedup for big comparisons and testing that the results

[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds

Nathaniel Smith added the comment: > a special case for WITH_CLEANUP_START I guess this works for the sync case, but it seems kinda fragile, and obviously won't work for the async case. Do you think it's worth revisiting this idea from the OP?: "The eval loop's "check for signal handlers" code

[issue27354] SSLContext.load_verify_locations cannot handle paths on Windows which cannot be encoded using mbcs

Ilya Kulakov added the comment: Christian, If you have windows under your hand and can try an alike path, you should see the problem right away if it's still there. I think the original problem was unnecessary PyUnicode_FSConverter: it failed to encode string into mbcs, while OpenSSL did not

[issue31252] Operator.itemgetter documentation should include dictionary keys example

Changes by Raymond Hettinger : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

<    1   2