[issue34142] Windows launcher version lookup flawed

LarryZA added the comment: https://docs.python.org/3/using/windows.html Section 3.4.4.2 -- ___ Python tracker ___ ___

[issue34142] Windows launcher version lookup flawed

Steve Dower added the comment: The behavior is correct, so the documentation needs fixing. Which page has that example on it? Is it assuming that you only have 3.1 installed? -- assignee: -> docs@python components: +Documentation nosy: +docs@python

[issue34134] multiprocessing memory huge usage

Xiang Zhang added the comment: Why accessing the result outside of with block? The pool is terminated while exiting the block before the work is done. -- ___ Python tracker

[issue34134] multiprocessing memory huge usage

Windson Yang added the comment: The code didn't work with imap because imap create a generator, so we can't access result outside the with statement. with Pool(os.cpu_count()) as p: result = p.imap(clean_up, k, 50) for r in result: print(r) In

[issue34132] Obscure netrc parser "bug"

Change by bbayles : -- keywords: +patch pull_requests: +7856 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue34142] Windows launcher version lookup flawed

New submission from LarryZA : In the manual it says that the following .ini file will cause the launcher to run Python3.1 for calls of `py` or `py -3` [defaults] python=3 python3=3.1 On my Windows 7 machine I have Python2.7-32, Python3.4-64, and Python3.7-64 (installed in that order).

[issue34133] ValueError documented as being restricted to only "a built-in operation or function"

Nathaniel Manista added the comment: Thank you both! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var

Alexander Mohr added the comment: we're compiling similar to debian and getting the same issues now only with 3.7 so interested in what the resolution is. I tried both w/ and w/o setting SOURCE_DATE_EPOCH and still get failures. -- nosy: +thehesiod

[issue33695] Have shutil.copytree(), copy() and copystat() use cached scandir() stat()s

Giampaolo Rodola' added the comment: Unless somebody has complaints I think I'm gonna merge this soon. -- ___ Python tracker ___

[issue34133] ValueError documented as being restricted to only "a built-in operation or function"

Raymond Hettinger added the comment: Nathaniel, thanks for the bug report. I've fixed the docs. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue34088] [EASY] sndhdr.what() throws exceptions on unknown files

Ammar Askar added the comment: Hey David, thanks for your contribution, I've added some feedback in context of the code on Github. -- ___ Python tracker ___

[issue34088] [EASY] sndhdr.what() throws exceptions on unknown files

david awad added the comment: Hey, I saw the issue and spent some time piecing together a PR for it. I've never contributed to Python before but this seemed like a good place to start! I posted these questions on the PR but I'll echo them here as well. - Should we only handle the specific

[issue34128] Release GIL periodically in _pickle module

Serhiy Storchaka added the comment: CPU = Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Ubuntu 18.04 Linux 4.15.0 x86_64 gcc 7.3.0 Performing the check in save() can have not insignificant overhead (especially after implementing the issue34141 optimization). It can be reduced if perform it when

[issue34088] [EASY] sndhdr.what() throws exceptions on unknown files

Change by david awad : -- keywords: +patch pull_requests: +7854 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue34128] Release GIL periodically in _pickle module

Change by ppperry : -- nosy: -ppperry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34128] Release GIL periodically in _pickle module

Antoine Pitrou added the comment: Interesting, which kind of computer / system / compiler are you on? -- ___ Python tracker ___

[issue34133] ValueError documented as being restricted to only "a built-in operation or function"

Brett Cannon added the comment: Just an FYI, Nathaniel, your title and message are bit "pushy". I've gone ahead and tweaked the title. -- nosy: +brett.cannon title: ValueError should not be documented as being restricted to only "a built-in operation or function" -> ValueError

[issue33111] Merely importing tkinter breaks parallel code (multiprocessing, sharedmem)

Terry J. Reedy added the comment: Ronald Oussoren> I can provide a patch, but that will likely be during EuroPython as I’m currently taking a roundabout route towards Edinburgh. Can you add a test of the procedure you document for using _tkinter with multiprocessing? --

[issue34140] Possible multiprocessing deadlock when placing too many objects in Queue()

Antoine Pitrou added the comment: Closing as not a bug. -- resolution: -> not a bug stage: -> resolved status: open -> closed type: performance -> behavior ___ Python tracker

[issue34140] Possible multiprocessing deadlock when placing too many objects in Queue()

Antoine Pitrou added the comment: The problem is you're joining the child processes before draining the queue in the parent. Generally, instead of building your own kind of synchronization like this, I would recommend you use the higher-level abstractions provided by multiprocessing.Pool

[issue34141] Speed up pickling simple non-recusive values

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +7853 stage: -> patch review ___ Python tracker ___ ___

[issue34141] Speed up pickling simple non-recusive values

New submission from Serhiy Storchaka : The proposed PR reduces an overhead of calling Py_EnterRecursiveCall() when pickle simple non-recusive values: None, True, False, instances of int, float, bytes, str. $ ./python -m timeit -s 'data = list(range(10**7)); import pickle' --

[issue34140] Possible multiprocessing deadlock when placing too many objects in Queue()

Change by Xiang Zhang : -- nosy: +davin, pitrou, xiang.zhang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34133] ValueError should not be documented as being restricted to only "a built-in operation or function"

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

[issue34133] ValueError should not be documented as being restricted to only "a built-in operation or function"

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

[issue34133] ValueError should not be documented as being restricted to only "a built-in operation or function"

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

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: The test fails on CPython master, so shouldn't it be removed? Don't we have a policy that all tests must pass on master? This is what I see: cpython38$ ./python.exe Lib/test/test_opcodes.py ./python.exe Lib/test/test_opcodes.py .F..

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

Serhiy Storchaka added the comment: New changeset fc153d127901361d7fe5f60caa6f41d2b8db0eb0 by Serhiy Storchaka in branch '2.7': [2.7] bpo-34068: iobase_close could call PyObject_SetAttrString with an exception set (GH-8282). (GH-8312) (GH-8314)

[issue34134] multiprocessing memory huge usage

Windson Yang added the comment: Thank you Xiang Zhang, I found the code keeps hanging when I use imap, I will try to figure out tomorrow. -- ___ Python tracker ___

[issue34136] Del on class __annotations__ regressed, failing test

Serhiy Storchaka added the comment: Sorry. I thought the discussion issue32550 shows that this CPython behavior change was intended, but it is not a part of Python language, and alternate implementations can have different behavior. But I expected that someone of participants with better

[issue34134] multiprocessing memory huge usage

Xiang Zhang added the comment: One thing worth a try here maybe turn `len` to `operator.length_hint`. But I am not sure it's a good idea and just a mention here. -- nosy: +xiang.zhang versions: -Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7

[issue34128] Release GIL periodically in _pickle module

Serhiy Storchaka added the comment: The demo script shows around 8% slowdown to me for data = list(map(float, range(N))) -- ___ Python tracker ___

[issue25150] 3.5: Include/pyatomic.h is incompatible with OpenMP (compilation of the third-party yt module fails on Python 3.5)

STINNER Victor added the comment: This issue is closed. Would you mind to either reopen it or create a new issue? -- ___ Python tracker ___

[issue34136] Del on class __annotations__ regressed, failing test

Guido van Rossum added the comment: Serhiy, what question do you want us to answer? On Tue, Jul 17, 2018 at 5:22 AM Serhiy Storchaka wrote: > > Change by Serhiy Storchaka : > > > -- > nosy: +Mark.Shannon, gvanrossum, levkivskyi > > ___ > Python

[issue34140] Possible multiprocessing deadlock when placing too many objects in Queue()

New submission from Horace Stoica : I am trying to use the multiprocessing module for a simulation on a spherical lattice, but the process hangs when the lattice is too large. In the file IssuesWithQueueMultiProcessing.py, the method createLattice(), use either "return(I4)" for the small

[issue33123] Path.unlink should have a missing_ok parameter

Daniel Pope added the comment: This would be a shortcut in the common case that you simply want an idempotent "make sure this file/symlink is gone" operation. There are already boolean options to enable idempotent behaviour in several pathlib implementations, such as mkdir(exist_ok=True)

[issue34128] Release GIL periodically in _pickle module

Antoine Pitrou added the comment: (as the demo script shows, there is no detectable slowdown) -- ___ Python tracker ___ ___

[issue34139] Remove stale unix datagram socket before binding

New submission from Quentin Dawans : Like https://github.com/python/asyncio/commit/806cc68d762acc30490cf5583569e41441c25c35 but for unix datagram socket. I'm looking into making a PR -- components: asyncio messages: 321829 nosy: asvetlov, qdawans, yselivanov priority: normal

[issue25150] 3.5: Include/pyatomic.h is incompatible with OpenMP (compilation of the third-party yt module fails on Python 3.5)

Antoine Pitrou added the comment: (see issue34128 for context) -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34128] Release GIL periodically in _pickle module

Antoine Pitrou added the comment: Attaching demonstration script. -- Added file: https://bugs.python.org/file47701/pickle_gil.py ___ Python tracker ___

[issue34128] Release GIL periodically in _pickle module

Antoine Pitrou added the comment: Attaching proof-of-concept patch. -- keywords: +patch Added file: https://bugs.python.org/file47700/pickle_gil.patch ___ Python tracker ___

[issue25150] 3.5: Include/pyatomic.h is incompatible with OpenMP (compilation of the third-party yt module fails on Python 3.5)

Antoine Pitrou added the comment: Case in point: if I want to include "internal/pystate.h" from _pickle.c, I get the following error: """ In file included from ./Include/internal/pystate.h:12:0, from /home/antoine/cpython/default/Modules/_pickle.c:10:

[issue25150] 3.5: Include/pyatomic.h is incompatible with OpenMP (compilation of the third-party yt module fails on Python 3.5)

Antoine Pitrou added the comment: I think this should be reconsidered. I understand the desire to compile Python with OpenMP. But the resolution here is hiding _Py_atomic symbols all the time, even when OpenMP isn't involved, and even when building a standard extension module. --

[issue34128] Release GIL periodically in _pickle module

Antoine Pitrou added the comment: The right way to do this is not to pass a timeout parameter but to check for GIL interrupts as done in the main bytecode evaluation loop. -- ___ Python tracker

[issue33123] Path.unlink should have a missing_ok parameter

Serhiy Storchaka added the comment: It can be written as try: path.inlink() except FileNotFoundError: pass If you want to save few lines of code, you can use contextlib.suppress(). with suppress(FileNotFoundError): path.inlink() I suggest to close this issue. It

[issue34128] Release GIL periodically in _pickle module

Martin Bammer added the comment: Maybe an optional parameter with the desired interval would be good idea. So that the coder can decide if he wants/needs that feature and which interval he needs for his application. Otherwise it is hard to define a specific interval which fits for everyone.

[issue34137] Add Path.lexist() to pathlib

e-kayrakli added the comment: I haven't contributed to Python yet and I can contribute this as a way for me to practice the PR process in Python. As this is a small addition, should I create a PR right away, or wait for a consensus here? -- nosy: +e-kayrakli

[issue34128] Release GIL periodically in _pickle module

Change by ppperry : -- components: +Library (Lib) title: Do not block threads when pickle/unpickle -> Release GIL periodically in _pickle module ___ Python tracker ___

[issue34138] RFC 6855 issue

New submission from Sam Varshavchik : Greetings. I am in the process of implementing RFC 6855 in Courier-IMAP. A Google search for IMAP clients that implement RFC 6855 led me to https://bugs.python.org/issue21800 and looking over the code that was added to imaplib, to support RFC 6855, a few

[issue34136] Del on class __annotations__ regressed, failing test

Change by Serhiy Storchaka : -- nosy: +Mark.Shannon, gvanrossum, levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

Serhiy Storchaka added the comment: > The assertion failure is a little bit "far" from the bug: would it make sense > to add "assert(!PyErr_Occurred());" to the entry point of: This looks like a part of larger issue, and I think it deserves a separate issue on the tracker. See also

[issue34136] Del on class __annotations__ regressed, failing test

Kay Hayen added the comment: Thanks for pointing out, where it comes from, Serhiy. So, should the test case be removed then. I still am not so sure about the bug nature. Because using the standard mechanism will do this: x : int class C: del __annotations__ x : float y : int

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

Change by Serhiy Storchaka : -- pull_requests: +7849 stage: resolved -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue34137] Add Path.lexist() to pathlib

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

Change by STINNER Victor : -- resolution: fixed -> status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

STINNER Victor added the comment: Python 2.7 also has the io module: it may be good to backport the change to Python 2.7 as well, no? I see the same bug in 2.7: res = PyObject_CallMethodObjArgs(self, _PyIO_str_flush, NULL); PyObject_SetAttrString(self, "__IOBase_closed", Py_True);

[issue34130] test_signal: test_warn_on_full_buffer() failed on AppVeyor

STINNER Victor added the comment: I succeeded to reproduce the issue on Windows, but I also got a failure of test_signal.test_socket() as if the C signal handle has not been called immediately by _testcapi.raise_signal() and so the socket didn't contain the byte of the signal number. It

[issue31342] test.bisect module causes tests to fail

STINNER Victor added the comment: > I considered adding a 'bisect' command to the test/__main__, e.g. you could > run 'python -m test --bisect ..'. That looks not entirely simple to > implement though. Ah yes, for the long term, integrating test.bisect directly in libregrtest would be

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

STINNER Victor added the comment: > The assertion failure is a little bit "far" from the bug: would it make sense > to add "assert(!PyErr_Occurred());" to the entry point of: Stefan, Serhiy: any opinion on my idea? For example, PyObject_HasAttr() can replace and clear the current exception

[issue33123] Path.unlink should have a missing_ok parameter

Change by Daniel Pope : -- nosy: +lordmauve ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34137] Add Path.lexist() to pathlib

New submission from Daniel Pope : When using pathlib to manipulate paths that may be symlinks or regular files, a pattern that comes up frequently is this expression: path.is_symlink() or path.exists() os.path.lexists(path) can be used for this, but when using pathlib going back to os.path

[issue33129] Add kwarg-only option to dataclass

Karthikeyan Singaravelan added the comment: There is an open PR and some discussion about this feature in attrs repo : https://github.com/python-attrs/attrs/pull/281 -- nosy: +xtreak ___ Python tracker

[issue34132] Obscure netrc parser "bug"

Karthikeyan Singaravelan added the comment: This seems to have been introduced with commit : 1df0f214a9fdb4dde7506576b144cf6a7fd01b65 before which it was working fine. Testing shows the error from 1df0f214a9fdb4dde7506576b144cf6a7fd01b65 and above. I have checked out only versions of

[issue34132] Obscure netrc parser "bug"

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34135] The results of time.tzname print broken.

Karthikeyan Singaravelan added the comment: There is some discussion about this at https://bugs.python.org/issue16322#msg251068 and seems the issue is a related one. Thanks -- nosy: +xtreak ___ Python tracker

[issue34136] Del on class __annotations__ regressed, failing test

Serhiy Storchaka added the comment: See issue32550. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing

[issue34136] Del on class __annotations__ regressed, failing test

New submission from Kay Hayen : I am getting this: PYTHONPATH=`pwd` /c/Python37_32/python test/test_opcodes.py .F.. == FAIL: test_do_not_recreate_annotations (__main__.OpcodeTest)

[issue34128] Do not block threads when pickle/unpickle

Serhiy Storchaka added the comment: A workaround is writing Python wrappers for IO: def Writer: def __init__(self, file): self.file = file def write(self, data): return self.file.write(data) def Reader: def __init__(self, file): self.file = file def

[issue24618] Invalid read in PyCode_New

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.4 ___ Python tracker

[issue33111] Merely importing tkinter breaks parallel code (multiprocessing, sharedmem)

Antoine Pitrou added the comment: It will definitely break *some* user code. Also, everyone not using tkinter (which I think is the majority of users) isn't affected by this. -- ___ Python tracker

[issue34128] Do not block threads when pickle/unpickle

Antoine Pitrou added the comment: This is about releasing the GIL periodically to allow other threads to run, as Python already does in its main interpreter loop. -- nosy: +pitrou versions: +Python 3.8 -Python 3.6 ___ Python tracker

[issue33111] Merely importing tkinter breaks parallel code (multiprocessing, sharedmem)

Ronald Oussoren added the comment: I can provide a patch, but that will likely be during EuroPython as I’m currently taking a roundabout route towards Edinburgh. Btw. I’m not sure yet how impactful changing the default spawning mechanism would be for 3.8. How likely is that to break user

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

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

[issue24618] Invalid read in PyCode_New

Serhiy Storchaka added the comment: New changeset cf30d5c5b88276a9af863438839ba386b9723a14 by Serhiy Storchaka in branch '3.6': bpo-24618: Add a check in the code constructor. (GH-8283) (GH-8311) https://github.com/python/cpython/commit/cf30d5c5b88276a9af863438839ba386b9723a14 --

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

Serhiy Storchaka added the comment: New changeset cc13016658a9ed86d0b702ab6c251ad5952a952f by Serhiy Storchaka in branch '3.6': bpo-34068: _io__IOBase_close_impl could call _PyObject_SetAttrId with an exception set (GH-8282). (GH-8312)

[issue34134] multiprocessing memory huge usage

Windson Yang added the comment: Thank you, I will try to make a pull request and let other to edit it. -- ___ Python tracker ___

[issue34118] Fix some class entries in 'Built-in Functions'

Raymond Hettinger added the comment: > How about a note under the index table: > Functions that must be classes are tagged *class*. < The iterator functions enumerate, filter, map, reversed, and zip > are classes in CPython, but they are not tagged because they > could be implemented as

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

miss-islington added the comment: New changeset 6020d98beaf6b9945beb7560f9a1df361e0ba4dd by Miss Islington (bot) in branch '3.7': bpo-34068: _io__IOBase_close_impl could call _PyObject_SetAttrId with an exception set (GH-8282)

[issue34133] ValueError should not be documented as being restricted to only "a built-in operation or function"

Change by Raymond Hettinger : -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list

[issue34133] ValueError should not be documented as being restricted to only "a built-in operation or function"

Change by Raymond Hettinger : -- keywords: +patch pull_requests: +7848 stage: -> patch review ___ Python tracker ___ ___

[issue34134] multiprocessing memory huge usage

INADA Naoki added the comment: > I think we should add something like "if you are using generator, consider > use imap instead" I think it's not good hint. There are short generator. And there are long (or infinite) iterator other than generator too. Maybe, "if iterator is not sequence

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

Change by Serhiy Storchaka : -- pull_requests: +7847 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34134] multiprocessing memory huge usage

Windson Yang added the comment: Thank you for the hint, INADA. I think we should add something like "if you are using generator, consider use imap instead" in https://docs.python.org/3.4/library/multiprocessing.html?highlight=process#multiprocessing.pool.Pool.map --

[issue24618] Invalid read in PyCode_New

Change by Serhiy Storchaka : -- pull_requests: +7846 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

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

[issue34068] traceback.clear_frames(): Objects/typeobject.c:3086: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.

Serhiy Storchaka added the comment: New changeset 28f07364f066792ceee93231dbb80ae8ad98b2bb by Serhiy Storchaka (Zackery Spytz) in branch 'master': bpo-34068: _io__IOBase_close_impl could call _PyObject_SetAttrId with an exception set (GH-8282)

[issue33967] functools.singledispatch: Misleading exception when calling without arguments

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