[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

[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

[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

[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

[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

[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()

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

[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 ->

[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,

[issue45723] Improve and simplify configure.ac checks

Change by Ant Man : -- nosy: +alwaysasetup ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[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,

[issue45723] Improve and simplify configure.ac checks

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

[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,

[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,

RE: Script profiling details

> You might try `py-spy`. That worked well, I started trying to get more data from the profile output with the stats module but didn't quite get there. Thank you everyone, jlc -- https://mail.python.org/mailman/listinfo/python-list

[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

[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 ___

[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

[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

[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 ___ ___

[issue46330] Simplify the signature of __exit__

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

Re: sharing data across Examples docstrings

On Wed, 12 Jan 2022 09:28:16 +1100, Cameron Simpson wrote: [...] > Personally I'd be inclined to put long identical examples in the class > docstring instead of the method, but that may not be appropriate. Good point, and perhaps it's best to put a comprehensive example in the class docstring,

[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 ___

[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

[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

[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

[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

[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 ___ ___

[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

[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

[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

[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

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

[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

[issue46347] memory leak in PyEval_EvalCodeEx

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

[issue46347] memory leak in PyEval_EvalCodeEx

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

[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

[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. --

[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

[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 ___

[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

[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. --

[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: 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

[issue46347] memory leak in PyEval_EvalCodeEx

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

[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

[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 --

[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

[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 ___

[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

[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

[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

Change by Yury Selivanov : -- pull_requests: +28752 pull_request: https://github.com/python/cpython/pull/30551 ___ 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:

[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

Re: sharing data across Examples docstrings

On 11Jan2022 16:09, Sebastian Luque wrote: >I am searching for a mechanism for sharing data across Examples >sections >in docstrings within a class. For instance: > >class Foo: > >def foo(self): >"""Method foo title > >The example generating data below may be much more

[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

[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 ->

[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 --

[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

[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

[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

[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

[issue46347] memory leak in PyEval_EvalCodeEx

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

[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

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

[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

[issue46347] memory leak in PyEval_EvalCodeEx

Pablo Galindo Salgado added the comment: Turns out this leak affects CYthon quite a lot: https://github.com/cython/cython/blob/29ad96444b8b1a4f05a6ac2328fde01de4782691/Cython/Utility/ObjectHandling.c#L2139-L2155 This seems to imply that every function call using __Pyx_PyCFunction_FastCall

[issue46347] memory leak in PyEval_EvalCodeEx

Yury Selivanov added the comment: New changeset 607d8a838f29ad3c4c4e85b39f338dade5f9cafe by Yury Selivanov in branch 'main': bpo-46347: Fix memory leak in PyEval_EvalCodeEx. (#30546) https://github.com/python/cpython/commit/607d8a838f29ad3c4c4e85b39f338dade5f9cafe --

[issue46347] memory leak in PyEval_EvalCodeEx

Change by miss-islington : -- nosy: +miss-islington nosy_count: 5.0 -> 6.0 pull_requests: +28750 pull_request: https://github.com/python/cpython/pull/30549 ___ Python tracker

[issue46350] re.sub, re.Match.expand, etc doesn't allow x, u, U, or N escapes in the template

Steven D'Aprano added the comment: It is better to raise each issue in its own ticket. You seem to have three distinct issues here: - The issue listed in the title, which I don't understand. A demonstration of the issue would be helpful. - The unrelated(?) issue of bad \N{} escapes, which

Re: sharing data across Examples docstrings

On Wed, Jan 12, 2022 at 9:11 AM Sebastian Luque wrote: > > Hello, > > I am searching for a mechanism for sharing data across Examples sections > in docstrings within a class. For instance: This seems like trying to cram too much information into the docstring, but oh well... do what you will.

[issue37295] Possible optimizations for math.comb()

Raymond Hettinger added the comment: I've been experimenting with a modification of Serhiy's recurrence relation, using a different value of j rather than j=k//2. The current design splits-off three ways when it recurses, so the number of calls grows quickly. For C(200,100), C(225,112),

[issue46350] re.sub, re.Match.expand, etc doesn't allow x, u, U, or N escapes in the template

New submission from Dan Snider : The docs use the phrase "unknown escapes of ASCII letters are reserved for future use and treated as errors". That seems ambiguous enough to question why "\x", "\u", "\U", and "\N{}" escapes aren't expanded in the template parameter like they are in patterns.

sharing data across Examples docstrings

Hello, I am searching for a mechanism for sharing data across Examples sections in docstrings within a class. For instance: class Foo: def foo(self): """Method foo title The example generating data below may be much more laborious. Examples

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

Steven D'Aprano added the comment: Many docstrings are only 1 line without being "See base class." And many docstrings are multiple lines while also referring the reader to see the parent class for further details. So this DWIM heuristic to guess whether or not to display a parent class

[issue46348] Modernize `test_typing`

Alex Waygood added the comment: Heh, no worries! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

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

New submission from Gregory P. Smith : Today `inspect.getdoc()` is quite simple. If a method has any docstring, it returns it. There is one idiom where this is not very useful to our users. A """See base class.""" docstring on a method. Rather than having to repeat the canonical base class

[issue46348] Modernize `test_typing`

Nikita Sobolev added the comment: Alex, thanks a lot for fixing so many of my titles! Highly appreciated! -- components: +Tests -Library (Lib) ___ Python tracker ___

[issue46348] Modernize `test_typing`

Change by Alex Waygood : -- nosy: +AlexWaygood, gvanrossum, kj title: Morernize `test_typing` -> Modernize `test_typing` type: -> behavior ___ Python tracker ___

[issue22833] The decode_header() function decodes raw part to bytes or str, depending on encoded part

Change by Daniel Lenski : -- keywords: +patch pull_requests: +28748 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30548 ___ Python tracker ___

[issue46348] Morernize `test_typing`

Change by Nikita Sobolev : -- keywords: +patch pull_requests: +28747 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30547 ___ Python tracker ___

[issue46348] Morernize `test_typing`

New submission from Nikita Sobolev : There are several very old details in `test_typing`. Some examples: 1. `@skipUnless(sys.version_info >= (3, 3), 'ChainMap was added in 3.3')` https://github.com/python/cpython/blame/dce642f24418c58e67fa31a686575c980c31dd37/Lib/test/test_typing.py#L3583

[issue46347] memory leak in PyEval_EvalCodeEx

Change by Yury Selivanov : -- keywords: +patch pull_requests: +28746 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30546 ___ Python tracker ___

[issue46347] memory leak in PyEval_EvalCodeEx

Elvis Pranskevichus added the comment: I can confirm that removing the kwargs allocation prevents the leak described in the asyncpg issue from happening. -- ___ Python tracker

[issue46347] memory leak in PyEval_EvalCodeEx

Yury Selivanov added the comment: This is the questionable place in the code: https://github.com/python/cpython/blob/dce642f24418c58e67fa31a686575c980c31dd37/Python/ceval.c#L6131-L6166 See that `kwargs` is allocated but never freed or used. --

Re: Why operations between dict views return a set and not a frozenset?

On 2022-01-11 19:49:20 +0100, Marco Sulla wrote: > I think this is what you mean: > > >>> dis.dis("for _ in {1, 2}: pass") > 1 0 SETUP_LOOP 12 (to 14) > 2 LOAD_CONST 3 (frozenset({1, 2})) > 4 GET_ITER > >>6 FOR_ITER

[issue46347] memory leak in PyEval_EvalCodeEx

Yury Selivanov added the comment: (this is the context of our current investigation btw: https://github.com/MagicStack/asyncpg/issues/874#issuecomment-1009383262) -- ___ Python tracker

[issue46347] memory leak in PyEval_EvalCodeEx

New submission from Yury Selivanov : I'm investigating a memory leak in 3.10, and while looking at the offending commit I stumbled upon this: in ceval.c:PyEval_EvalCodeEx, there's this allocation: PyObject **kwargs = PyMem_Malloc(sizeof(PyObject *)*kwcount); The problem is that this

Re: A Newspaper for Python Mailing Lists

On 2022-01-11 12:38:44 -0800, Paul Bryan wrote: > Subscribed. ️ Same. hp -- _ | Peter J. Holzer| Story must make more sense than reality. |_|_) || | | | h...@hjp.at |-- Charles Stross, "Creative writing __/ | http://www.hjp.at/ |

[issue46346] New compilation warnings on Windows

Change by Christian Heimes : -- dependencies: +_Py_stat and _Py_wstat using incorrect type for status argument nosy: +christian.heimes, pablogsal priority: normal -> release blocker stage: -> needs patch type: -> behavior ___ Python tracker

Re: A Newspaper for Python Mailing Lists

Subscribed. ️ On Wed, 2022-01-12 at 00:35 +0400, Abdur-Rahmaan Janhangeer wrote: > Added RSS: > > 2.0 unless later versions have some advantages: > > https://pyherald.com/rss.xml > > Kind Regards, > > Abdur-Rahmaan Janhangeer > about | blog  > github > Mauritius > --

Re: A Newspaper for Python Mailing Lists

Added RSS: 2.0 unless later versions have some advantages: https://pyherald.com/rss.xml Kind Regards, Abdur-Rahmaan Janhangeer about | blog github Mauritius > --

[issue46237] Incorrect line reported in syntax error

Terry J. Reedy added the comment: I understand. I think that for IDLE, I should check that the error .text is in the line indicated, and if not, recover somehow rather than blindly marking the the indicated column. For a shell statement entry, try to find the right line. Not sure for an

[issue46249] [sqlite3] move set lastrowid out of the query loop and enable it for executemany()

Erlend E. Aasland added the comment: > You don't know on which cursor the last row was inserted [...] SQLite has no concept of cursors :) > It also seems that the function really only works for INSERTs and > not for UPDATEs. Yes, hence it's name: sqlite3_last_insert_rowid() ! > I'd suggest

[issue46249] [sqlite3] move set lastrowid out of the query loop and enable it for executemany()

Marc-Andre Lemburg added the comment: On 11.01.2022 20:46, Erlend E. Aasland wrote: > > If we are to revert to this behaviour, we'll have to start examining the SQL > we are given (search for INSERT and REPLACE keywords, determine if they are > valid (i.e. not a comment, not part of a column

[issue45729] [doc] "history and license" link has wrong target

Change by miss-islington : -- pull_requests: +28745 pull_request: https://github.com/python/cpython/pull/30541 ___ Python tracker ___

[issue45729] [doc] "history and license" link has wrong target

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +28744 pull_request: https://github.com/python/cpython/pull/30540 ___ Python tracker

[issue46346] New compilation warnings on Windows

Steve Dower added the comment: Possibly related to Victor's change in issue46303? -- nosy: +vstinner ___ Python tracker ___ ___

[issue46249] [sqlite3] move set lastrowid out of the query loop and enable it for executemany()

Erlend E. Aasland added the comment: > OTOH, the SQLite API is tied to the _connection_ object, so it may not make > sense to align it with lastrowid which is a _cursor_ attribute. That came out weird; let's try again: The SQLite API is tied to the _connection_ object, so it may not make

  1   2   >