[issue40521] [subinterpreters] Make free lists and unicode caches per-interpreter

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

[issue46006] [subinterpreter] _PyUnicode_EqualToASCIIId() issue with subinterpreters

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

[issue44899] tarfile: add support for creating an archive of potentially changing files

Change by Marko Tuononen : -- pull_requests: +28632 pull_request: https://github.com/python/cpython/pull/30426 ___ Python tracker ___

[issue46275] caret location for syntax error pointing with f-strings

Change by Pablo Galindo Salgado : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44665] asyncio.create_task() documentation should mention user needs to keep reference to the task

Alexander Hartl added the comment: I just found this PR when a task of mine spontaneously crashed with a "Task was destroyed but it is pending" in the middle of program execution. I think the warning should be added to `loop.create_task()`, too. Not sure if `loop.call_later()` and

[issue22739] "There is no disk in the drive" error

Pop Expangea added the comment: Forgot to comment versions: pdoc: 8.1.0 Python: 3.8.7 Platform: Windows-7-6.1.7601-SP1 -- ___ Python tracker ___

[issue46274] backslash creating statement out of nothing

Change by Pablo Galindo Salgado : -- nosy: -pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46277] '''...''' error

STINNER Victor added the comment: vstinner@apu$ python3 Python 3.10.1 (main, Dec 9 2021, 00:00:00) [GCC 11.2.1 20211203 (Red Hat 11.2.1-7)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> str_='''... ... ... ... .. ... .. ... . ... ... ... ''' >>> str_

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: Marked as a release blocker. See python-committers post: https://mail.python.org/archives/list/python-committ...@python.org/thread/7OWGAL4UL5HNKKQFUGH6N6L4JDVPEN7R/ -- priority: normal -> release blocker ___

[issue22739] "There is no disk in the drive" error

Pop Expangea added the comment: Probably not a Python bug, but I have detected this problem a couple of times, and it always happened the same way, while using pdoc package in a Python script. Steps to reproduce the behavior: 1. Connect mobile telephone (Avenzo Xirius 5.5 AV112) to my

[issue41011] [venv] record which executable and command were used to create a virtual environment

Vinay Sajip added the comment: New changeset f4e325c21d6d9c2bf70224dc69d707b226f87872 by andrei kulakov in branch 'main': bpo-41011: venv -- add more variables to pyvenv.cfg (GH-30382) https://github.com/python/cpython/commit/f4e325c21d6d9c2bf70224dc69d707b226f87872 --

[issue45723] Improve and simplify configure.ac checks

Christian Heimes added the comment: Thanks William! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46276] ImportError: DLL load failed while importing

Eryk Sun added the comment: > ImportError: DLL load failed while importing _socket: El parámetro no es > correcto. I'm not familiar with the implementation of PyInstaller, which is a third-party tool. The above invalid-parameter error may be indirectly related to the problem with frida, or

[issue45661] [meta] Freeze commonly used stdlib modules.

Inada Naoki added the comment: I don't against deep freezing functools and contextlib. But I think we should optimize and utilize zipimport or something similar, because we can not deep-freeze all stdlib or 3rd party libraries. See also:

[issue46288] Migrating python 2.7 to 3.6 using 2to3 tool

New submission from Karthik S : Greeting of the day to all.. I would like to address few queries as mentioned in the below. python 2.7 code is running fine on RHEL 7.9,we are migrating to python3 from Python2 using 2to3 on RHEL 7.9. After migrating, When we run our products in python 3.6,we

[issue45723] Improve and simplify configure.ac checks

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

[issue45723] Improve and simplify configure.ac checks

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

[issue40521] [subinterpreters] Make free lists and unicode caches per-interpreter

STINNER Victor added the comment: My commit ea251806b8d11b30d2182af1e589caf88acf (interned strings) introduced bpo-46006 "[subinterpreter] _PyUnicode_EqualToASCIIId() issue with subinterpreters" regression. To unblock the Python 3.11.0a4 release, I just reverted the change. It

[issue26571] turtle regression in 3.5

William Navaraj added the comment: Hi all, Sorry. I seem to have stepped on someone's toes or no one likes turtle any more (as this is active since 2016). As you can see, I am new here and still getting a feel for these procedures. I was preparing a Jupyter notebook for my students. I

[issue46263] FreeBSD buildbots cannot compile Python

Christian Heimes added the comment: New changeset b259015c1079744dbe3d58bd4c27757a6df9d1c6 by Miss Islington (bot) in branch '3.9': [3.9] bpo-46263: FreeBSD 14.0 jemalloc workaround for junk bytes of freed memory (GH-30434) (GH-30437)

[issue46263] FreeBSD buildbots cannot compile Python

Eric Snow added the comment: In summary, regarding the test_embed failure: > FWIW: from test_embed.test_init_setpythonhome: > > if not config['executable']: > config['use_frozen_modules'] = -1 > > From the buildbot test stdout (but not pythoninfo) I see that >

[issue34602] python3 resource.setrlimit strange behaviour under macOS

Ronald Oussoren added the comment: > My understanding of the resolution of this ticket is that it is still not > possible to use setrlimit with RLIMIT_STACK to raise the soft stack limit. > Is that correct? Yes, the code in msg324731 still fails. We're still using the mechanism described

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: AFAICS, the test_embed failure first appeared after GH-29041 (bpo-45582) was merged. After GH-29041, there has been numerous fixes for test_embed: $ git log --oneline | grep bpo-45582 3f398a77d3 bpo-45582: Fix test_embed failure during a PGO build

[issue46244] typing._TypeVarLike missing __slots__

Change by Alex Waygood : -- nosy: +AlexWaygood ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45665] Problems caused by isinstance(list[int], type) returning True

Alex Waygood added the comment: > We will still allow instantiating e.g. list[int], right? I certainly hope so! That would be a much more breaking change if we were to change that, and I can't personally see any benefit to doing so. -- ___ Python

[issue46282] print() docs do not indicate its return value

Steven D'Aprano added the comment: Sure, there will always be some users who will find certain things not obvious. Sometimes I'm that user myself. What did this user think print() returned? What precisely was their question? Perhaps if I saw the conversation in context, I would be more

[issue46263] FreeBSD buildbots cannot compile Python

Eric Snow added the comment: A FreeBSD builder where it's working: AMD64 FreeBSD Shared 3.x (koobs-freebsd-564d) OS: FreeBSD 14.0-CURRENT main-n244626-cb7cc72c546: GENERIC-NODEBUG (amd64) System: 2-core, 8Gb, VirtualBox (6.x) Guest Features: - Compiler: FreeBSD clang version 11.0.1

[issue46142] python --help output is too long

Éric Araujo added the comment: Victor said on github that he would prefer `--help-xoptions` to `-X help`. It would align with `--help` and `--help-env`, but not with other `-X abc` options. I think that `--help-X` may be better, as it uses the same form (`X`) rather than the non-word

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: Also, AMD64 FreeBSD Shared 3.x is configured --with-pydebug and --enable-shared. I'd be surprised if those were the root cause of this though. Both buildbots are in-tree builds. FWIW, my FreeBSD 14.0-CURRENT main-n250453-7ac82c96fe7 VM also fails, as

[issue46263] FreeBSD buildbots cannot compile Python

Pablo Galindo Salgado added the comment: Unfortunately the buildbots are still red: https://buildbot.python.org/all/#/builders/483/builds/1416/steps/5/logs/stdio https://buildbot.python.org/all/#/builders/172/builds/1102 One is the test_embed problem with frozen modules:

[issue46031] add POP_JUMP_IF_NOT_NONE and POP_JUMP_IF_NONE

Mark Shannon added the comment: New changeset 3db762db72cc0da938614b1e414abb1e12ca4094 by penguin_wwy in branch 'main': bpo-46031: add POP_JUMP_IF_NOT_NONE and POP_JUMP_IF_NONE (GH-30019) https://github.com/python/cpython/commit/3db762db72cc0da938614b1e414abb1e12ca4094 -- nosy:

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: FYI, the buildbot has Python 3.9.9 installed, as seen from the configure step. (nit: it's pkg install python39, not pkg install python3.9) -- ___ Python tracker

[issue46270] Comparison operators in Python Tutorial 5.7

Jan added the comment: Sounds reasonable. -- resolution: works for me -> fixed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue46039] Break up the YIELD_FROM instruction.

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

[issue45256] Remove the usage of the C stack in Python to Python calls

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

[issue40222] "Zero cost" exception handling

Mark Shannon added the comment: Yes. -- priority: release blocker -> resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

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

[issue46280] About vulnerabilities in Cpython native code

New submission from Xinrong Lin <414039...@qq.com>: I am currently doing some research on the security of CPython. I used the open source vulnerability analysis engine, Infer(https://fbinfer.com/), to scan the native code of CPython 3.10.0. The scan results show that there are still a

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

miss-islington added the comment: New changeset cb0683128b8f413e0f16293752014902d4de4984 by Miss Islington (bot) in branch '3.9': bpo-46278: fix typo introduced in GH-30427 (GH-30430) https://github.com/python/cpython/commit/cb0683128b8f413e0f16293752014902d4de4984 --

[issue46006] [subinterpreter] _PyUnicode_EqualToASCIIId() issue with subinterpreters

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

[issue40521] [subinterpreters] Make free lists and unicode caches per-interpreter

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

[issue46282] print() docs do not indicate its return value

Change by James Gerity : -- keywords: +patch pull_requests: +28642 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30435 ___ Python tracker ___

[issue46263] FreeBSD buildbots cannot compile Python

miss-islington added the comment: New changeset a4aa52dc2801d25b6343fe2ef8de7f40ea3bc883 by Christian Heimes in branch 'main': bpo-46263: FreeBSD 14.0 jemalloc workaround for junk bytes of freed memory (GH-30434)

[issue46263] FreeBSD buildbots cannot compile Python

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

[issue46263] FreeBSD buildbots cannot compile Python

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

[issue46283] [subinterpreters] Unicode interned strings must not be shared between interpreters

New submission from STINNER Victor : My commit ea251806b8d11b30d2182af1e589caf88acf made Unicode interned strings per interpreter to avoid accessing the same Python object from two different interpreters, to avoid race conditions on its reference count. Problem: the change introduced the

[issue46280] About vulnerabilities in Cpython native code

Zachary Ware added the comment: As an aside, there's an issue with Roundup where a username composed of all digits causes it to think that name is a user ID in the nosy list. I recommend changing your username to include a non-digit character so that others can interact with you on your

[issue46284] DirEntry returns invalid values for is_dir and is_file on NFS

New submission from Nicolas SURRIBAS : Hello, I bumped into this strange behavior several times when using os.scandir on mounted NFS shares. I'm using Python 3.9.1 >>> path = b'/mnt/nfs_share/sdb1/System Volume Information/' >>> l = list(os.scandir(path)) >>> print(l[2].name)

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: > Note that in-tree builds are working find on other platforms, AFAICS. Yes, almost all of the buildbots are using in-tree builds. IIRC, buildbots for out-of-tree builds were added just recently. -- ___ Python

[issue46280] About vulnerabilities in Cpython native code

Joannah Nanjekye added the comment: > You mention here that your tool automatically "repairs" the code. Could you > >submit a sample PR with the repairs that your tool does so we can evaluate > it? I second this. I obviously, am assuming good intentions from the author, not experimenting

[issue46282] print() docs do not indicate its return value

James Gerity added the comment: The original question was closer to the related issue of "indicate return types for all built-ins," conversation log follows (UTC-5): ``` 09:33:50 ringo__ | is there a stdlib api docs which actually has *full* functions signature?

[issue46283] [subinterpreters] Unicode interned strings must not be shared between interpreters

Change by STINNER Victor : -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46256] Objects __del__ called after module have been removed

Daniele Varrazzo added the comment: Thank you @pablogsal. For me it was surprising as never seen before 3.10 instance. If this is the expected behaviour (and the stdlib expects it) we can try and take the same type of care in psycopg. -- ___

[issue46282] print() docs do not indicate its return value

James Gerity added the comment: I opened this ticket on behalf of a user who asked about print() specifically in #python on the Libera IRC network, who I assume does not find this obvious. I don't think it would be tenable to add this note to every built-in, but that's not the intended

[issue46263] FreeBSD buildbots cannot compile Python

Guido van Rossum added the comment: Is this under control, or do you still need help with some part? (Are there two separate issues or not?)-- --Guido (mobile) -- ___ Python tracker

[issue46282] print() docs do not indicate its return value

Barry A. Warsaw added the comment: I think it does a better service to users to explain how Python returns None implicitly if a function doesn't have any other explicit return value. If the print() docs had this note, it would be confusing why other similar functions don't. It's also

[issue46263] FreeBSD buildbots cannot compile Python

Christian Heimes added the comment: test_capi is fixed now. test_embed is still an issue. -- ___ Python tracker ___ ___

[issue46263] FreeBSD buildbots cannot compile Python

Pablo Galindo Salgado added the comment: > Is this under control, or do you still need help with some part? As Christian mentions, we still have the test_embed issue -- ___ Python tracker

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: > the test_embed failure first appeared after GH-29041 (bpo-45582) was merged. Make that "first appeared on FreeBSD". Also, numerous was perhaps an exaggeration. Make that a few :) -- ___ Python tracker

[issue46272] Fix bitwise and logical terminology in python.gram

Raymond Hettinger added the comment: > comparison::= or_expr (comp_operator or_expr)* So, the meaning of these names like this is, "lt followed by an optional bitwise_or expression"? compare_op_bitwise_or_pair[CmpopExprPair*]: | eq_bitwise_or | noteq_bitwise_or |

[issue46263] FreeBSD buildbots cannot compile Python

Guido van Rossum added the comment: IIUC Steve is still on vacation, so we shouldn't wait for him to fix this. -- ___ Python tracker ___

[issue32696] Fix pickling exceptions with multiple arguments

Change by Georg Brandl : -- nosy: -georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37287] [doc] Add section on pickling to exceptions documentation

Irit Katriel added the comment: This is the same as issue32696. I'm turning this into a documentation issue. -- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python, iritkatriel title: picke cannot dump Exception subclasses with different super()

[issue40545] Expose _PyErr_GetTopmostException

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

[issue46263] FreeBSD buildbots cannot compile Python

Eric Snow added the comment: I just put up a PR that should fix the failure. -- ___ Python tracker ___ ___ Python-bugs-list

[issue46006] [subinterpreter] _PyUnicode_EqualToASCIIId() issue with subinterpreters

STINNER Victor added the comment: _PyUnicode_EqualToASCIIId() and type update_slot() functions are fixed in 3.10 and main branches. The regression is now fixed. But the revert reintroduces the issue on subinterpreters, so I created bpo-46283: "[subinterpreters] Unicode interned strings must

[issue46263] FreeBSD buildbots cannot compile Python

miss-islington added the comment: New changeset b951dec4418326c06d493020dadedf85a3b29a82 by Miss Islington (bot) in branch '3.10': bpo-46263: FreeBSD 14.0 jemalloc workaround for junk bytes of freed memory (GH-30434)

[issue46280] About vulnerabilities in Cpython native code

Change by Zachary Ware : -- nosy: +414039482 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32696] Fix pickling exceptions with multiple arguments

Irit Katriel added the comment: This isn't really an issue with exceptions, it's just that __reduce__ goes out of sync with the object's constructor signature. Here's a simple example of the same: class Base: def __init__(self, msg): self.msg = msg def __reduce__(self):

[issue32696] Fix pickling exceptions with multiple arguments

Change by Irit Katriel : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue29466] pickle does not serialize Exception __cause__ field

Irit Katriel added the comment: > Attributes __context__, __cause__ and __traceback__ are not pickled. The > traceback objects are even not pickleable. It's not guaranteed that the __cause__ and __context__ are picklable either. Should we try to pickle them, or should we document this and

[issue46263] FreeBSD buildbots cannot compile Python

Eric Snow added the comment: Just to be clear, the test_embed failure is on AMD64 FreeBSD Non-Debug 3.x (https://buildbot.python.org/all/#/builders/172). I agree that 99fcf15052 (bpo-45582: Port getpath[p].c to Python (GH-29041)) is likely to be the cause. -- nosy: +steve.dower

[issue46263] FreeBSD buildbots cannot compile Python

Change by Eric Snow : -- pull_requests: +28645 pull_request: https://github.com/python/cpython/pull/30438 ___ Python tracker ___

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Steve Dower added the comment: I'm happy with PR 30362 now - any other comments before we merge? -- ___ Python tracker ___ ___

[issue46277] '''...''' error

Mark Dickinson added the comment: https://github.com/ipython/ipython/issues/12843 looks very closely related, and may be the exact same bug. -- nosy: +mark.dickinson ___ Python tracker

[issue33857] python exception on Solaris : code for hash blake2b was not found

Irit Katriel added the comment: Python 3.6 is no longer maintained. Please create a new issue if you are seeing this problem on a current (>= 3.9) version of Python. -- nosy: +iritkatriel resolution: -> out of date stage: -> resolved status: open -> closed

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by Andrew Svetlov : -- components: +asyncio nosy: +yselivanov versions: +Python 3.10, Python 3.11, Python 3.9 ___ Python tracker ___

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

New submission from Andrew Svetlov : Actual implementations of asyncio event loops (both Unix and Windows) support contextvars and accept `context` argument in `loop.call_*()` methods. Abstract event loop definition doesn't it. It is not a bug but a signature incompatibility that can

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by Andrew Svetlov : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: Here's a strange observation from my FreeBSD 14.0 VM: With system supplied python3.8 (dependency of the git package), test_embed succeeds. If I explicitly install python3.9 (pkg install python3.9 installs Python 3.9.9), rebuild and test, test_embed

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Kumar Aditya added the comment: The PR introduced a typo in the method signature see https://github.com/python/cpython/pull/30427#discussion_r779497305 -- nosy: +kumaraditya303 ___ Python tracker

[issue46279] [docs] Minor information-ordering issue in __main__ doc

New submission from FeRD (Frank Dana) : The expanded documentation on top-level environments is quite an improvement, but there's one passage that causes some confusion. In the section '__main__.py in Python Packages', towards the end, it reads: """ This won’t work for __main__.py files in

[issue46031] add POP_JUMP_IF_NOT_NONE and POP_JUMP_IF_NONE

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

[issue46256] Objects __del__ called after module have been removed

Christopher Vickery added the comment: This it very clear and totally consistent with the observed behavior. I can think of a couple of workarounds for my app (move the db access from module initialization to a function that gets invoked "on demand", or redirect sys.stderr to /dev/null just

[issue46263] FreeBSD buildbots cannot compile Python

Christian Heimes added the comment: $ PYTHONMALLOC=malloc_debug ./python t.py Traceback (most recent call last): File "/usr/home/heimes/dev/python/cpython/t.py", line 4, in _testcapi.check_pyobject_freed_is_freed() ^ _testcapi.error:

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

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

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Andrew Svetlov added the comment: New changeset 861a9aaf0f517623c58ca4eb5588804b2632fcba by Miss Islington (bot) in branch '3.10': bpo-46278: fix typo introduced in GH-30427 (GH-30430) (GH-30431) https://github.com/python/cpython/commit/861a9aaf0f517623c58ca4eb5588804b2632fcba --

[issue46263] FreeBSD buildbots cannot compile Python

Change by Christian Heimes : -- pull_requests: +28641 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/30434 ___ Python tracker ___

[issue46006] [subinterpreter] _PyUnicode_EqualToASCIIId() issue with subinterpreters

STINNER Victor added the comment: New changeset 72c260cf0c71eb01eb13100b751e9d5007d00b70 by Victor Stinner in branch '3.10': [3.10] bpo-46006: Revert "bpo-40521: Per-interpreter interned strings (GH-20085)" (GH-30422) (GH-30425)

[issue40521] [subinterpreters] Make free lists and unicode caches per-interpreter

STINNER Victor added the comment: New changeset 72c260cf0c71eb01eb13100b751e9d5007d00b70 by Victor Stinner in branch '3.10': [3.10] bpo-46006: Revert "bpo-40521: Per-interpreter interned strings (GH-20085)" (GH-30422) (GH-30425)

[issue46276] ImportError: DLL load failed while importing

Eric V. Smith added the comment: I see this has been reported in frida's tracker. It looks like a problem with that package. -- nosy: +eric.smith type: crash -> behavior ___ Python tracker

[issue46263] FreeBSD buildbots cannot compile Python

Erlend E. Aasland added the comment: Wait a minute. It is not tied to the Python version installed; it seems to be an issue with in-tree vs. out-of-tree builds. The failed build was in-tree. The build that succeeded was out-of-tree. I did a new build with Python 3.9 installed, which

[issue46276] ImportError: DLL load failed while importing

Eryk Sun added the comment: "_frida.cp310-win_amd64.pyd" is a bad build or corrupted file. It imports a procedure with no name from a DLL with no name, which causes the loader to search for a file named ".DLL". Even if that were found, it imports another procedure with no name or correct

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

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

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

miss-islington added the comment: New changeset b50e5e916a05df65ab6a255af7624b751e0fe9d1 by Kumar Aditya in branch 'main': bpo-46278: fix typo introduced in GH-30427 (GH-30430) https://github.com/python/cpython/commit/b50e5e916a05df65ab6a255af7624b751e0fe9d1 --

[issue46225] f_lasti behaves differently for lambdas returned from loops

Mark Shannon added the comment: Are you using `f_lasti == -1` as a proxy for "is this an actual call or a resumption after a yield"? Ultimately PEP 669 will provide all the information you could need to differentiate different events. In the meantime... We now make all "call" events

[issue46282] print() docs do not indicate its return value

New submission from Steven D'Aprano : Do the print docs need to mention something so obvious? Functions and methods which operate by side-effect typically don't mention that they return None, see for example the docs for various builtin methods:

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +28633 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30427 ___ Python tracker ___

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by Kumar Aditya : -- pull_requests: +28634 pull_request: https://github.com/python/cpython/pull/30430 ___ Python tracker ___

[issue46166] Get "self" args or non-null co_varnames from frame object with C-API

Change by Mark Shannon : -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

  1   2   >