[issue39778] collections.OrderedDict and weakref.ref raises "refcount is too small" assertion

Raymond Hettinger added the comment: False alarm. I misread the diff. All is well. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue43760] The DISPATCH() macro is not as efficient as it could be (move PyThreadState.use_tracing)

Change by Guido van Rossum : -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue45116] Performance regression 3.10b1 and later on Windows: Py_DECREF() not inlined in PGO build

Change by Guido van Rossum : -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue45250] Make sure documentation is accurate for what an (async) iterable and (async) iterator are

New submission from Brett Cannon : There's some inaccuracies when it comes to iterable and iterators (async and not). See https://mail.python.org/archives/list/python-...@python.org/thread/3W7TDX5KNVQVGT5CUHBK33M7VNTP25DZ/#3W7TDX5KNVQVGT5CUHBK33M7VNTP25DZ for background. Should probably chec

[issue45226] Misleading error message when pathlib.Path.symlink_to() fails with permissions error

Barney Gale added the comment: `os.symlink()` and `pathlib.Path.symlink_to()` have reversed argument orders, but in the repro steps you're supplying arguments in the same order. -- nosy: +barneygale ___ Python tracker

[issue45246] the sorted() documentation should refer to operator

Raymond Hettinger added the comment: -0 on this. While it is true that __lt__ is used, we don't really want people to exploit that fact. Doing so will get them into trouble elsewhere. For example, max(seq) uses __gt__. Also, when mixing types, a return of NotImplemented will trigger a ca

[issue21302] time.sleep (floatsleep()) should use clock_nanosleep() on Linux

Change by STINNER Victor : -- pull_requests: +26882 pull_request: https://github.com/python/cpython/pull/28483 ___ Python tracker ___ __

[issue21302] time.sleep (floatsleep()) should use clock_nanosleep() on Linux

STINNER Victor added the comment: wait.py: script to test the time.sleep() function. Press CTRL+C multiple times during the sleep to check that even if the sleep is interrupted, time.sleep() sleeps the expected duration. -- Added file: https://bugs.python.org/file50289/wait.py _

[issue45251] signal.SIGCLD alias is not available on OSX

New submission from Thomas Caswell : The module attribute signal.SIGCLD (https://docs.python.org/3/library/signal.html#signal.SIGCLD) is an "archaic" (quoting from the GNU C Library source) alias for signal.SIGCHLD (https://docs.python.org/3/library/signal.html#signal.SIGCHLD). signal.SIGCHLD

[issue24076] sum() several times slower on Python 3 64-bit

Raymond Hettinger added the comment: > I created a PR from my last patch, inlining the unpacking > of single digit integers. Thanks, that gets to the heart of the issue. I marked the PR as approved (though there is a small coding nit you may want to fix). -- _

[issue24076] sum() several times slower on Python 3 64-bit

Guido van Rossum added the comment: The patch looks fine, but it looks a bit like benchmark chasing. Is the speed of builtin sum() of a sequence of integers important enough to do this bit of inlining? (It may break if we change the internals of Py_Long, as Mark Shannon has been wanting to d

[issue45252] Missing support for Source Specific Multicast

New submission from CireSnave : It appears that Python's socket module is missing support for the IGMPv3 socket options needed to support Source Specific Multicast. Many developers appear to be adding the necessary constants through something like: if not hasattr(socket, "IP_UNBLOCK_SOURCE")

[issue45234] copy_file raises FileNotFoundError when src is a directory

Change by Andrei Kulakov : -- nosy: +kj ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue45249] Syntax error location range indicator does not work in doctests

Andrei Kulakov added the comment: Thinking a bit more on this, I'm not sure this can be closed, as SyntaxError indicators seems not to be working. I'm not sure if this is limited to doctests or not. I've updated the title to narrow it down to SyntaxErrors. I can look more into this if needed

[issue45249] SyntaxError location range indicator does not work in doctests

Change by Andrei Kulakov : -- title: Syntax error location range indicator does not work in doctests -> SyntaxError location range indicator does not work in doctests ___ Python tracker _

[issue24076] sum() several times slower on Python 3 64-bit

Stefan Behnel added the comment: > The patch looks fine, but it looks a bit like benchmark chasing. Is the speed > of builtin sum() of a sequence of integers important enough to do this bit of > inlining? Given that we already accepted essentially separate loops for the int, float and every

[issue24076] sum() several times slower on Python 3 64-bit

Guido van Rossum added the comment: Sounds good, you have my blessing. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45116] Performance regression 3.10b1 and later on Windows: Py_DECREF() not inlined in PGO build

neonene added the comment: I built 3.10rc2 PGO with PR28475 applied, and posted the inliner's log. In the log, the 4-callees mentioned above are now inlined, which were "hard reject"ed before. As for the performance, a few reporters may be needed, but it's not necessary for them to care abou

[issue45176] Many regtest failures on Windows with non-ASCII account name

Ming Hua added the comment: Steve Dower (steve.dower) posted: > I'd guess that these tests are assuming that sys.executable contains only > ASCII characters. All the tests run in a non-ASCII working directory, so it's > only the runtime that is not tested propersy here. > > The easiest way f

[issue45116] Performance regression 3.10b1 and later on Windows: Py_DECREF() not inlined in PGO build

Ma Lin added the comment: PR28475: 64-bit build is 1.03x slower than 28d28e0~1 32-bit build is 1.04x slower than 28d28e0~1 28d28e0~1 is the last good commit. -- ___ Python tracker __

<    1   2