[issue35101] inspect.findsource breaks on class frame objects

Change by Aivar Annamaa : -- nosy: +Aivar.Annamaa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34766] BaseProxy cache should be cleaned when Manager client is reconnected

Change by Karthikeyan Singaravelan : -- nosy: +davin, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35826] Typo in example for async with statement with condition

Change by Kevin Mai-Hsuan Chia : -- keywords: +patch, patch, patch, patch pull_requests: +11511, 11512, 11513, 11514 stage: -> patch review ___ Python tracker ___

[issue35826] Typo in example for async with statement with condition

Change by Kevin Mai-Hsuan Chia : -- keywords: +patch, patch, patch pull_requests: +11511, 11512, 11514 stage: -> patch review ___ Python tracker ___

[issue35826] Typo in example for async with statement with condition

Change by Kevin Mai-Hsuan Chia : -- keywords: +patch pull_requests: +11511 stage: -> patch review ___ Python tracker ___ ___

[issue35826] Typo in example for async with statement with condition

Change by Kevin Mai-Hsuan Chia : -- keywords: +patch, patch pull_requests: +11511, 11512 stage: -> patch review ___ Python tracker ___

[issue35045] test_min_max_version (test.test_ssl.ContextTests) fails on Fedora 29+ and openssl 1.1.1

Change by Alan Huang : -- pull_requests: +11509, 11510 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35045] test_min_max_version (test.test_ssl.ContextTests) fails on Fedora 29+ and openssl 1.1.1

Change by Alan Huang : -- pull_requests: +11509 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35831] Format Spec example says limited to 3.1+ but works in 2.7

Fred L. Drake, Jr. added the comment: The 3.X docs generally don't refer to the 2.X series. What that comment is pointing out is that leaving the field identifier out (the number inside the {...} placeholder syntax) was not in the 3.0, but added in 3.1. Unfortunately, I don't have a 3.0

[issue35831] Format Spec example says limited to 3.1+ but works in 2.7

Change by Mitchell L Model : -- assignee: -> docs@python components: +Documentation nosy: +docs@python ___ Python tracker ___ ___

[issue35831] Format Spec example says limited to 3.1+ but works in 2.7

New submission from Mitchell L Model : https://docs.python.org/3/library/string.html#format-examples includes this line: '{}, {}, {}'.format('a', 'b', 'c') # 3.1+ only This does in fact work in 2.7. I don't see anything special about this -- seems an entirely straightforward format.

[issue35830] building multiple (binary) packages from a single project

Éric Araujo added the comment: The way to achieve this is to make sure your two components live in two separate directories, each with its setup.py. This is the simple way that works with distutils/setuptools and pip install-from-vcs (you can install from a subdir of a repo). --

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Change by Steve Dower : -- assignee: -> steve.dower resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue35830] building multiple (binary) packages from a single project

Stefan Seefeld added the comment: Yes. Depending on the answer to my question(s), the request either becomes: "please add support for this use-case", or "this use-case isn't documented properly", i.e. a feature request or a bug report. You choose. :-) --

[issue35830] building multiple (binary) packages from a single project

Steven D'Aprano added the comment: This is a bug tracker for reporting bugs and enhancement requests, not a help desk. Do you have a *specific* feature request or a bug to report? If not, you should ask this on a community forum such as Stackoverflow, Reddit's r/learnpython, the

[issue35830] building multiple (binary) packages from a single project

New submission from Stefan Seefeld : I'm working on a project that I'd like to split into multiple separately installable components. The main component is a command-line tool without any external dependencies. Another component is a GUI frontend that adds some third-party dependencies.

[issue34691] _contextvars missing in xmaster branch Windows build?

Change by Carol Willing : -- nosy: +willingc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35826] Typo in example for async with statement with condition

Change by Carol Willing : -- nosy: +willingc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

miss-islington added the comment: New changeset a6a8524bb1c78c7425346ec20ecffc02d1d02a79 by Miss Islington (bot) in branch '3.7': bpo-35811: Avoid propagating venv settings when launching via py.exe (GH-11677) https://github.com/python/cpython/commit/a6a8524bb1c78c7425346ec20ecffc02d1d02a79

[issue35656] More matchers in unittest.mock

Yash Aggarwal added the comment: > due to floating-point inexactness +1 Its not easy to predict when calculated value will not be equal to expected theoretical value. for example math.cos(radians(90)) is something like 6e-17 rather than 0. Testing for this exact value would be just awkward.

[issue35829] datetime: parse "Z" timezone suffix in fromisoformat()

rdb added the comment: > > From a cursory glance at the RFC3339 spec it looks like the only other > > change needed to fully support RFC3339 would be to support an arbitrary > > number of sub-second digits, whereas fromisoformat() currently requires > > either exactly 3 or 6. > > There are

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

miss-islington added the comment: New changeset 6a9c0fca3f2f93681468b51929472f4433753f25 by Miss Islington (bot) in branch '3.7': bpo-35797: Fix default executable used by the multiprocessing module (GH-11676) https://github.com/python/cpython/commit/6a9c0fca3f2f93681468b51929472f4433753f25

[issue35826] Typo in example for async with statement with condition

Yury Selivanov added the comment: Please submit a PR! -- components: +asyncio -Documentation keywords: +easy nosy: +asvetlov, yselivanov ___ Python tracker ___

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Steve Dower added the comment: I realised while doing the fix that changing sys.executable to point to the "real" python.exe would break scenarios that involve generating scripts. All of those have been relying on sys.executable launching the venv, which would break if we changed it there.

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Change by miss-islington : -- pull_requests: +11503, 11504, 11505 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Change by miss-islington : -- pull_requests: +11506, 11507, 11508 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Change by miss-islington : -- pull_requests: +11503 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Change by miss-islington : -- pull_requests: +11506 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Steve Dower added the comment: New changeset 4e02f8f8b4baab63f927cfd87b401200ba2969e9 by Steve Dower in branch 'master': bpo-35797: Fix default executable used by the multiprocessing module (GH-11676) https://github.com/python/cpython/commit/4e02f8f8b4baab63f927cfd87b401200ba2969e9

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Change by miss-islington : -- pull_requests: +11506, 11507 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Steve Dower added the comment: New changeset adad9e68013aac166c84ffe4e23f3a5464f41840 by Steve Dower in branch 'master': bpo-35811: Avoid propagating venv settings when launching via py.exe (GH-11677) https://github.com/python/cpython/commit/adad9e68013aac166c84ffe4e23f3a5464f41840

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Change by miss-islington : -- pull_requests: +11503, 11504 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35829] datetime: parse "Z" timezone suffix in fromisoformat()

Paul Ganssle added the comment: > I can see your point in not causing confusion about what this method is > meant to be used for. In this case, making it easy to explain what it does is less important than making the scope and contract of the function clear so that we don't have to argue

[issue35766] Merge typed_ast back into CPython

Guido van Rossum added the comment: The PR is ready for reviews now. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35829] datetime: parse "Z" timezone suffix in fromisoformat()

rdb added the comment: I'm a fan of "be lenient in what you accept" but I can see your point in not causing confusion about what this method is meant to be used for. Because what I'm trying to use it for technically falls outside the intended use, I say it would make the most sense to

[issue34623] _elementtree.c doesn't call XML_SetHashSalt()

Matej Cepl added the comment: > Will this change be backported to 3.5 and 3.4? It applied cleanly on both > however on 3.4 there is a test failure: It actually haven't applied cleanly to me on Python 3.4.6 (SLE-12 package). Apparently self->parser has to be changed into self_xp->parser.

[issue35829] datetime: parse "Z" timezone suffix in fromisoformat()

Paul Ganssle added the comment: You can see the discussion in bpo-15873 for the full rationale of why "Z" was omitted - to quote from https://bugs.python.org/issue15873#msg307607 : > We can have further discussion later about what exactly should be supported > in Python 3.8, > but even in

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Change by Steve Dower : -- keywords: +patch, patch, patch pull_requests: +11500, 11501, 11502 stage: test needed -> patch review ___ Python tracker ___

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Change by Steve Dower : -- keywords: +patch pull_requests: +11500 stage: test needed -> patch review ___ Python tracker ___ ___

[issue35811] py.exe should unset the __PYVENV_LAUNCHER__ environment variable

Change by Steve Dower : -- keywords: +patch, patch pull_requests: +11500, 11501 stage: test needed -> patch review ___ Python tracker ___

[issue35825] Py_UNICODE_SIZE=4 fails to link on Windows

Terry J. Reedy added the comment: I think this falls in the category of "don't do that", because Windows does not support wide builds. If so, this issue should be closed as 'not a bug'. If not, some Windows expert should enlighten me. -- nosy: +terry.reedy

[issue35798] duplicate SyntaxWarning: "is" with a literal

Terry J. Reedy added the comment: I verified that master on Windows (which requires " instead of ') > python -c "if object() is 42: pass" results in the doubled messsage, and that after applying PR 11639 and recompiling, there is only 1 message. We should test that exactly 1 warning is

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Change by Steve Dower : -- keywords: +patch, patch, patch pull_requests: +11497, 11498, 11499 stage: test needed -> patch review ___ Python tracker ___

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Change by Steve Dower : -- keywords: +patch, patch pull_requests: +11497, 11498 stage: test needed -> patch review ___ Python tracker ___

[issue35797] concurrent.futures.ProcessPoolExecutor does not work in venv on Windows

Change by Steve Dower : -- keywords: +patch pull_requests: +11497 stage: test needed -> patch review ___ Python tracker ___ ___

[issue35829] datetime: parse "Z" timezone suffix in fromisoformat()

Change by Karthikeyan Singaravelan : -- nosy: +belopolsky, p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35829] datetime: parse "Z" timezone suffix in fromisoformat()

New submission from rdb : The fromisoformat() function added in 3.7 is a very welcome addition. But one quite noticeable absence was the inability to parse Z instead of +00:00 as the timezone suffix. Its absence is particularly noticeable given how ubiquitous use of Z is in ISO 8601

[issue35782] Missing whitespace after comma in randrange raise error

Terry J. Reedy added the comment: We usually don't backport exception message changes, for the reason given, unless the content is wrong or misleading. Unless Raymond says otherwise, I think the backport should be closed as too trivial and this issue closed as fixed. -- nosy:

[issue35808] Let's retire pgen

Change by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35815] Able to instantiate a subclass with abstract methods from __init_subclass__ of the ABC

Change by Karthikeyan Singaravelan : -- nosy: +rhettinger, stutzbach ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35800] remove smtpd.MailmanProxy

Change by Samuel Colvin : -- keywords: +patch, patch, patch pull_requests: +11494, 11495, 11496 stage: -> patch review ___ Python tracker ___

[issue35800] remove smtpd.MailmanProxy

Change by Samuel Colvin : -- keywords: +patch, patch pull_requests: +11494, 11495 stage: -> patch review ___ Python tracker ___

[issue35800] remove smtpd.MailmanProxy

Change by Samuel Colvin : -- keywords: +patch pull_requests: +11494 stage: -> patch review ___ Python tracker ___ ___

[issue35823] Use vfork() in subprocess on Linux

Ronald Oussoren added the comment: BTW. I hadn't noticed _close_open_fds_safe, that should be safe when using vfork(). Finally: I have no strong opinion on this patch, your explanation looks fine and I'm not up-to-speed w.r.t. implementation details of vfork and the like to feel

[issue35707] time.sleep() should support objects with __float__

Change by Jeroen Demeyer : -- components: +Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35821] Clarify when logging events are propagated when propagate is true

Chris Jerdonek added the comment: I'm not sure which part of what I wrote you think is inaccurate. All of what you wrote matches what I was trying to convey. For example, my saying "pass to the parent logger" corresponds to the "set current logger to parent" box in the diagram. And by

[issue35823] Use vfork() in subprocess on Linux

Change by STINNER Victor : -- pull_requests: +11492, 11493 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35823] Use vfork() in subprocess on Linux

Change by STINNER Victor : -- pull_requests: +11492 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue30548] typo in documentation for create_autospec

Cheryl Sabella added the comment: Mario is right that this isn't a typo. Here's a code example to illustrate what he said: >>> class MyClass: ... a = 3 ... def foo(self): pass ... >>> mock_class = create_autospec(MyClass) >>> mock_class >>> mock_class() >>> mock_class.foo >>>

[issue35821] Clarify when logging events are propagated when propagate is true

Vinay Sajip added the comment: That isn't quite accurate. A logger's attached handlers will always be offered a chance to handle an event if the logger's level and filters allow. However, the event is not actually passed to ancestor loggers - it is directly offered to any handlers attached

[issue35828] test_multiprocessing_* tests - success versus fail varies over time

New submission from Michael Felt : Last August I started running a bot for AIX using xlc_r as the compiler, rather than gcc that the other AIX bot uses. Initially, I had no issues with the test_multiprocess* tests, but of late (last two+ months I am guessing) I have been having regular

[issue35224] PEP 572: Assignment Expressions

STINNER Victor added the comment: Note: I checked and 3.x buildbots are back to green (ignoring the ones which already failed previously). Good. -- ___ Python tracker ___

[issue34134] multiprocessing memory huge usage

Antoine Pitrou added the comment: This is basically fixed, except that I'll let the Release Manager choose whether 3.6 gets the fix as well. Thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7

[issue34134] multiprocessing memory huge usage

Antoine Pitrou added the comment: New changeset c2674bf11036af1e06c1be739f0eebcc72dfbf7a by Antoine Pitrou (Miss Islington (bot)) in branch '3.7': bpo-34134: Advise to use imap or imap_unordered when handling long iterables. (gh-8324) (gh-11673)

[issue35827] C API dictionary views type checkers are not documented

New submission from Ori Avtalion : dictobject.h defines several helpers to ease checking of dictionary view types. If they are meant to be part of the API, they should be documented. PyDictKeys_Check PyDictItems_Check PyDictValues_Check PyDictViewSet_Check Should they be added to dict.rst,

[issue34134] multiprocessing memory huge usage

Change by miss-islington : -- pull_requests: +11489, 11490, 11491 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34134] multiprocessing memory huge usage

Change by miss-islington : -- pull_requests: +11489, 11490 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34134] multiprocessing memory huge usage

Change by miss-islington : -- pull_requests: +11489 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34134] multiprocessing memory huge usage

Change by miss-islington : -- pull_requests: +11487, 11488 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34134] multiprocessing memory huge usage

Change by miss-islington : -- pull_requests: +11487 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34134] multiprocessing memory huge usage

Antoine Pitrou added the comment: New changeset 3bab40db96efda2e127ef84e6501fda0cdc4f5b8 by Antoine Pitrou (Windson yang) in branch 'master': bpo-34134: Advise to use imap or imap_unordered when handling long iterables. (gh-8324)

[issue35823] Use vfork() in subprocess on Linux

Alexey Izbyshev added the comment: > W.r.t. closing all file descriptors > 2: posix_spawn_file_actions_addclose > can do this when using posix_spawn. That would have a performance cost, you'd > basically have to resort to closing all possible file descriptors and cannot > use the smarter

[issue35823] Use vfork() in subprocess on Linux

Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31171] multiprocessing.BoundedSemaphore of 32-bit python could not work while cross compiling on linux platform

Barry Davis added the comment: The behaviour I saw (32-bit only) was a python process getting stuck. I got this from strace: ... futex(0xb5acc000, FUTEX_WAIT, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0xb5acc000, FUTEX_WAIT, 0, NULL) = -1 EAGAIN (Resource temporarily

[issue31171] multiprocessing.BoundedSemaphore of 32-bit python could not work while cross compiling on linux platform

Barry Davis added the comment: I've just hit this issue using Python-2.7.9, gcc-8.1.0, glibc-2.23. The patch I made to fix the issue based on comments in this issue: --- Python-2.7.9/setup.py 2019-01-25 09:30:39.049501423 + +++ Python-2.7.9/setup.py 2019-01-25

[issue35826] Typo in example for async with statement with condition

Kevin Mai-Hsuan Chia added the comment: In the [example](https://docs.python.org/3.8/library/asyncio-sync.html#asyncio.Condition) of the equivalent code to the `async with` statement: ```python cond = asyncio.Condition() # ... later await lock.acquire() try: await cond.wait() finally:

[issue35826] Typo in example for async with statement with condition

New submission from Kevin Mai-Hsuan Chia : In the [example](https://docs.python.org/3.8/library/asyncio-sync.html#asyncio.Condition) of the equivalent code to the `async with statement`: ```python cond = asyncio.Condition() # ... later await lock.acquire() try: await cond.wait() finally:

[issue35825] Py_UNICODE_SIZE=4 fails to link on Windows

New submission from Kristof Niederholtmeyer : When I change Py_UNICODE_SIZE from 2 (default) to 4 in PC/pyconfig.h, msvc-14 gives the following error: _winreg.obj : error LNK2001: unresolved external symbol PyUnicode_DecodeMBCS

[issue35810] Object Initialization Bug with Heap-allocated Types

Stefan Behnel added the comment: It seems right that a heap allocate object owns a reference to its (non-static) type. But the mere fact that you had to adapt stdlib code makes it obvious that this will also break existing user code out there. And such breakage is very likely to remain