[issue46347] memory leak in PyEval_EvalCodeEx

Larry Hastings added the comment: The function will still leak "kwnames" and "default" if creating the "func" object fails. Admittedly that would only happen in a low-memory condition which is a) rare and b) probably only happens just before the interpreter completely dies, so it's not wort

[issue46347] memory leak in PyEval_EvalCodeEx

Larry Hastings added the comment: (Sorry--it'll leak "kwnames", "newargs", and "defaults".) -- ___ Python tracker ___ ___ Python-bu

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

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

[issue46347] memory leak in PyEval_EvalCodeEx

Pablo Galindo Salgado added the comment: Apparently, this is causing adyncpg to leak megabytes in seconds -- ___ Python tracker ___ ___

[issue37295] Possible optimizations for math.comb()

Change by Raymond Hettinger : Removed file: https://bugs.python.org/file50555/comb_pole.py ___ Python tracker ___ ___ Python-bugs-list maili

[issue33125] Windows 10 ARM64 platform support

Tommy Vercetti added the comment: Hi Steve, We appreciate your interest in OBS Studio! In my opinion, the installer doesn't have or need to be in ARM64, because it's not more complex than copying files and writing registry keys, and as an installer, it should be the most forgotten part of

[issue37295] Possible optimizations for math.comb()

Raymond Hettinger added the comment: One fixup: - j = min(k // 2, FixedJ) + j = FixedJ if k > FixedJ else k // 2 With that fix, the number of 64-bit mod arithmetic calls drops to 3, 4, and 20 for C(200,100), C(225,112), and C(250,125). The compares to 115, 150, and 193 calls in t

[issue46320] runtime/interp/thread state refactoring leads to segmentation fault

Eric Snow added the comment: > pip install -r dev-requirements.txt > pip install ".[socks,secure,brotli]" > pytest I was able to reproduce the crash with these steps. Thanks! -- ___ Python tracker

[issue46347] memory leak in PyEval_EvalCodeEx

miss-islington added the comment: New changeset b1a94f1fab7c0aee0705483616a1b2c3f2713c00 by Miss Islington (bot) in branch '3.10': bpo-46347: Fix memory leak in PyEval_EvalCodeEx. (GH-30546) https://github.com/python/cpython/commit/b1a94f1fab7c0aee0705483616a1b2c3f2713c00 -- __

[issue46346] New compilation warnings on Windows

STINNER Victor added the comment: Oh right, I introduced these warnings in bpo-46303. Let's continue the discussion there. -- dependencies: -_Py_stat and _Py_wstat using incorrect type for status argument priority: release blocker -> resolution: -> duplicate stage: needs patch -> r

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

STINNER Victor added the comment: I marked bpo-46346 as a duplicate of this issue. Copy of the first message: """ I am getting these warnings: C:\Users\gvanrossum\cpython\PC\_testconsole.c(70,38): warning C4013: '_Py_get_osfhandle' undefined; assuming extern returnin g int [C:\Users\gvanross

[issue46347] memory leak in PyEval_EvalCodeEx

STINNER Victor added the comment: The memory leak has been fixed in 3.10 and main branches. Can this issue be closed now? -- components: +Interpreter Core versions: +Python 3.10, Python 3.11 ___ Python tracker

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

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

[issue46347] memory leak in PyEval_EvalCodeEx

Change by Yury Selivanov : -- pull_requests: +28752 pull_request: https://github.com/python/cpython/pull/30551 ___ Python tracker ___ __

[issue40059] Provide a toml module in the standard library

Shantanu added the comment: This is now PEP 680: https://www.python.org/dev/peps/pep-0680/ Currently being discussed at: https://discuss.python.org/t/pep-680-tomllib-support-for-parsing-toml-in-the-standard-library/13040 -- ___ Python tracker

[issue46347] memory leak in PyEval_EvalCodeEx

Yury Selivanov added the comment: > The function will still leak "kwnames" and "default" if creating the "func" > object fails. Yeah, here's another PR to address that: https://github.com/python/cpython/pull/30551 -- ___ Python tracker

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

Change by Christian Heimes : -- priority: normal -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

Christian Heimes added the comment: I set the release blocker flag for the ticket. -- nosy: +christian.heimes ___ Python tracker ___ __

[issue46351] Makefile missing '/' for some path names

New submission from Guntram Wolski : In reviewing the output of make -n install, I notice certain paths are missing '/' separators: if test "x" != "x" ; then \ rm -f /usr/local/python3.9.9/binpython3.9-32; \ lipo \ -output /usr/local/python3.9.9/bin/python3.9-

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

STINNER Victor added the comment: New changeset 08bc1bad11cad39f508bd662c9b28fcd9c995512 by Victor Stinner in branch 'main': bpo-46303: Fix fileutils.h compiler warnings (GH-30550) https://github.com/python/cpython/commit/08bc1bad11cad39f508bd662c9b28fcd9c995512 --

[issue46347] memory leak in PyEval_EvalCodeEx

Yury Selivanov added the comment: New changeset 20b5791ce9b47195ce51cfd5acb223b1ca59cdf0 by Yury Selivanov in branch 'main': bpo-46347: Fix PyEval_EvalCodeEx to correctly cleanup in error paths (#30551) https://github.com/python/cpython/commit/20b5791ce9b47195ce51cfd5acb223b1ca59cdf0 --

[issue46347] memory leak in PyEval_EvalCodeEx

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

STINNER Victor added the comment: Christian Heimes: "I set the release blocker flag for the ticket." It's just a compiler warning, why marking it as a release blocker? Anyway, it's now fixed. -- priority: release blocker -> ___ Python tracker

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

STINNER Victor added the comment: Paul: Can you please try to build the main branch of Python with clang and tell me if you still have the compiler warnings? If yes, can you please copy/paste the compiler warnings? Do you build Python on Windows or from another OS (cross-compilation)? -

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

STINNER Victor added the comment: If possible, I would prefer to not change 3.9 and 3.10 to avoid any risk of introducing a *new* build error, while trying to support a new platform. I don't think that we currently supporting build Python with clang on Windows yet. -- __

[issue46320] runtime/interp/thread state refactoring leads to segmentation fault

Eric Snow added the comment: FYI, I get the crash with just: pytest test/contrib/test_pyopenssl.py::TestHTTPS::test_verify_none_and_bad_fingerprint -- ___ Python tracker __

[issue40280] Consider supporting emscripten/webassembly as a build target

Change by Christian Heimes : -- pull_requests: +28753 pull_request: https://github.com/python/cpython/pull/30552 ___ Python tracker ___

[issue39298] add BLAKE3 to hashlib

Jack O'Connor added the comment: Ah, good idea. I've published the new C implementation as: https://test.pypi.org/project/blake3-experimental-c/ You can install it with: pip install -i https://test.pypi.org/simple/ blake3-experimental-c Despite the package name change, the extension module

[issue39298] add BLAKE3 to hashlib

Larry Hastings added the comment: So, can we shoot for adding this to 3.11? Jack, do you consider the code is in good shape? I'd be up for shepherding it along in the process. In particular, I can contribute the bindings so BLAKE3 is a first-class citizen of hashlib. -- _

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

Paul Campbell added the comment: Hi Victor, I was trying to compile with clang on Windows 10. I will try to pull your 3.11 changes and test. Sorry to cause so much churn. It looked to me like a simple issue that was missed, probably because whatever was trying to compile was not normally com

[issue46347] memory leak in PyEval_EvalCodeEx

Change by Yury Selivanov : -- pull_requests: +28754 pull_request: https://github.com/python/cpython/pull/30553 ___ Python tracker ___ __

[issue46347] memory leak in PyEval_EvalCodeEx

Change by Yury Selivanov : -- pull_requests: +28755 pull_request: https://github.com/python/cpython/pull/30554 ___ Python tracker ___ __

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

Christian Heimes added the comment: It's unlikely that you can reproduce the issue with clang. We use MSVC and a manually maintained pyconfig.h on Windows. -- ___ Python tracker

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

STINNER Victor added the comment: > Hi Victor, I was trying to compile with clang on Windows 10. I will try to > pull your 3.11 changes and test. Sorry to cause so much churn. It looked to > me like a simple issue that was missed, probably because whatever was trying > to compile was not nor

[issue46347] memory leak in PyEval_EvalCodeEx

Yury Selivanov added the comment: New changeset 6f9ca53a6ac343a5663cc5c52546acf9a63b605a by Yury Selivanov in branch '3.10': bpo-46347: Fix PyEval_EvalCodeEx to correctly cleanup in error paths (#30553) https://github.com/python/cpython/commit/6f9ca53a6ac343a5663cc5c52546acf9a63b605a --

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

Paul Campbell added the comment: > In Python, we are trying to provide a same C API on all platforms. If "struct > stat" is no longer considered as portable, IMO we should attempt to avoid it, > at least in the public C API. Microsoft provides stat and struct stat, but they prepend the names

[issue46320] runtime/interp/thread state refactoring leads to segmentation fault

Eric Snow added the comment: It looks like PyThreadState.async_exc is getting set to 0x01 somewhere. There isn't any code like that in https://github.com/python/cpython/commit/32a67246b0d1e08cd50fc3bfa58052cfeb515b2e. However, the struct layout of PyThreadState did change slightly in that

[issue46347] memory leak in PyEval_EvalCodeEx

Yury Selivanov added the comment: New changeset be578e0c063dad1dbb273f86d5bc77e4e6f14583 by Yury Selivanov in branch 'main': bpo-46347: Yet another fix in the erorr path of PyEval_EvalCodeEx (#30554) https://github.com/python/cpython/commit/be578e0c063dad1dbb273f86d5bc77e4e6f14583 -

[issue46338] libc_ver() runtime error when sys.executable is empty

Allie Hammond added the comment: Thanks for getting back to me so quickly! It's an empty string -- ___ Python tracker ___ ___ Pytho

[issue46349] inspect.getdoc() should append parent class method docs when encountering a local one line docstring

Gregory P. Smith added the comment: >From the context of help(typical_subclass_of_abstract_thing.method), the user >isn't told what the base classes are or which one might have documentation. >So it could become an exercise in frustration. and LOL yes the parameter name is silly but that's

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

STINNER Victor added the comment: > Seems it would go back to depending on some type nonstandard python macro to > translate between the two during build. In the internal C API, there are less concerns about writing portable code. We expect users of this API to pay more attention to what the

[issue46347] memory leak in PyEval_EvalCodeEx

Gregory P. Smith added the comment: when was the regression introduced? I wouldn't necessarily rush an urgent release out unless this was just introduced in the 3.10.1 patch release. Could it wait for 3.10.2 already scheduled for four weeks from now? -- nosy: +gregory.p.smith

[issue46347] memory leak in PyEval_EvalCodeEx

Elvis Pranskevichus added the comment: The leak was introduced in 3.10a5 (https://github.com/python/cpython/commit/0332e569c12d3dc97171546c6dc10e42c27de34b) -- ___ Python tracker ___

[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument

Paul Campbell added the comment: Victor: The changes in the main branch gets me past this issue without having to make additional changes. -- ___ Python tracker ___ _

[issue46330] Simplify the signature of __exit__

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue46142] python --help output is too long

Éric Araujo added the comment: The PR now has --help-env, --help-xoptions and --help-all ! -- ___ Python tracker ___ ___ Python-bugs

[issue46303] Building Python with clang on Windows fails on _Py_stat(): struct stat is not defined

STINNER Victor added the comment: Paul Campbell: "The changes in the main branch gets me past this issue without having to make additional changes." Ok, nice. I close the issue. I consider that building Python with clang is a new feature. I prefer to not backport these changes to 3.9 and 3.

[issue46347] memory leak in PyEval_EvalCodeEx

Pablo Galindo Salgado added the comment: > Could it wait for 3.10.2 already scheduled for four weeks from now? I don't feel comfortable leaving a ton of Cython functions leaking memory constantly on many function calls. According to https://github.com/MagicStack/asyncpg/issues/874 asyncpg ca

[issue46020] Optimize long_pow for the common case

Change by Tim Peters : -- keywords: +patch pull_requests: +28756 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30555 ___ Python tracker ___ _

[issue46020] Optimize long_pow for the common case

Tim Peters added the comment: GH_30555 helps a bit by leaving the giant-exponent table of small odd powers as uninitialized stack trash unless it's actually used. -- ___ Python tracker _

[issue46314] Stray RESUME opcode for unused lambda

Change by Ant Man : -- components: +2to3 (2.x to 3.x conversion tool), Argument Clinic, Build, C API, Cross-Build, Demos and Tools, Distutils, Documentation, Extension Modules, FreeBSD, IDLE, IO, Installation, Library (Lib), Parser, Regular Expressions, SSL, Subinterpreters, Tests, T

[issue46314] Stray RESUME opcode for unused lambda

Change by Larry Hastings : -- components: -2to3 (2.x to 3.x conversion tool), Argument Clinic, Build, C API, Cross-Build, Demos and Tools, Distutils, Documentation, Extension Modules, FreeBSD, IDLE, IO, Installation, Library (Lib), Parser, Regular Expressions, SSL, Subinterpreters,

[issue45723] Improve and simplify configure.ac checks

Change by Ant Man : -- type: enhancement -> security ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue45723] Improve and simplify configure.ac checks

Change by Ant Man : -- components: +2to3 (2.x to 3.x conversion tool), Argument Clinic, C API, Cross-Build, Demos and Tools, Distutils, Documentation, Extension Modules, FreeBSD, IDLE, IO, Installation, Interpreter Core, Library (Lib), Parser, Regular Expressions, SSL, Subinterpreter

[issue45723] Improve and simplify configure.ac checks

Change by Ant Man : -- nosy: +alwaysasetup ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue45723] Improve and simplify configure.ac checks

Change by Zachary Ware : -- components: -2to3 (2.x to 3.x conversion tool), Argument Clinic, C API, Cross-Build, Demos and Tools, Distutils, Documentation, Extension Modules, FreeBSD, IDLE, IO, Installation, Interpreter Core, Library (Lib), Parser, Regular Expressions, SSL, Subinter

[issue46314] Stray RESUME opcode for unused lambda

Change by Zachary Ware : -- nosy: -Alex.Willmer, asvetlov, barry, dstufft, eric.araujo, ezio.melotti, koobs, lys.nikolaou, mrabarnett, ned.deily, paul.moore, r.david.murray, ronaldoussoren, steve.dower, terry.reedy, tim.golden, vstinner, yselivanov, zach.ware type: security -> behav

[issue37295] Possible optimizations for math.comb()

Tim Peters added the comment: Just noting that comb_pole.py requires a development version of Python to run (under all released versions, a byteorder argument is required for int.{to, from}_byte() calls). -- ___ Python tracker

[issue37295] Possible optimizations for math.comb()

Raymond Hettinger added the comment: Just posted an update that runs on 3.8 or later. -- Added file: https://bugs.python.org/file50557/comb_pole.py ___ Python tracker ___

[issue37295] Possible optimizations for math.comb()

Change by Raymond Hettinger : Removed file: https://bugs.python.org/file50556/comb_pole.py ___ Python tracker ___ ___ Python-bugs-list maili

[issue46352] Steps To Do Arlo Setup

Change by Jacob Martin : -- components: Installation files: Arlo camera setup.jpg nosy: jacobmartin717 priority: normal severity: normal status: open title: Steps To Do Arlo Setup type: security versions: Python 3.8 Added file: https://bugs.python.org/file50558/Arlo camera setup.jpg __

[issue46320] runtime/interp/thread state refactoring leads to segmentation fault

Quentin Pradet added the comment: Oh my god. You're right, I had a cffi wheel compiled for Python 3.11 before that commit. But the wheel was not coming from PyPI, it was coming from pip's own cache! And we recently enabled pip's cache in GitHub Actions too. So the wheel compiled locally for a

[issue46159] Segfault when using trace functions in 3.11a3

Quentin Pradet added the comment: The ABI between alpha 2 and alpha 3 changed, see https://bugs.python.org/issue46320. If pip built (say) cffi in CI for alpha2 and put it in the cache, then it reused that wheel for alpha3 and the segfault is expected. -- nosy: +Quentin.Pradet _

[issue46352] Spam

Change by Dennis Sweeney : -- components: -Installation nosy: -jacobmartin717 resolution: -> not a bug stage: -> resolved status: open -> closed title: Steps To Do Arlo Setup -> Spam type: security -> versions: -Python 3.8 ___ Python tracker <

<    1   2