[issue44812] [docs] Document PyMember_{Get/Set}One in C API reference

Change by Łukasz Langa : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44812] [docs] Document PyMember_{Get/Set}One in C API reference

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

[issue44812] [docs] Document PyMember_{Get/Set}One in C API reference

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

[issue44812] [docs] Document PyMember_{Get/Set}One in C API reference

Change by Ken Jin : -- keywords: +patch pull_requests: +26061 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27555 ___ Python tracker ___

[issue44812] [docs] Document PyMember_{Get/Set}One in C API reference

: docs@python components: Documentation messages: 398777 nosy: docs@python, kj, petr.viktorin priority: normal severity: normal status: open title: [docs] Document PyMember_{Get/Set}One in C API reference versions: Python 3.10, Python 3.11, Python 3.9 ___ Python

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

Change by Łukasz Langa : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.11 -Python 3.8 ___ Python tracker ___

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

Łukasz Langa added the comment: New changeset b57011d2a5375bc9f255361dc64c9e6fbc203e0e by Miss Islington (bot) in branch '3.9': bpo-41911: Update docs for various expressions (GH-27470) (GH-27491) https://github.com/python/cpython/commit/b57011d2a5375bc9f255361dc64c9e6fbc203e0e --

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

Łukasz Langa added the comment: New changeset 843b3d28209b7754c51c6cc3844f66808b6dbdaf by Miss Islington (bot) in branch '3.10': bpo-41911: Update docs for various expressions (GH-27470) (GH-27490) https://github.com/python/cpython/commit/843b3d28209b7754c51c6cc3844f66808b6dbdaf --

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

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

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

Łukasz Langa added the comment: New changeset 4bd9caafb64589288e5171087070bde726178c58 by andrei kulakov in branch 'main': bpo-41911: Update docs for various expressions (GH-27470) https://github.com/python/cpython/commit/4bd9caafb64589288e5171087070bde726178c58 -- nosy:

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

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

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Roundup Robot : -- pull_requests: +25992 pull_request: https://github.com/python/cpython/pull/27473 ___ Python tracker ___

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

Andrei Kulakov added the comment: I've put up a PR here: https://github.com/python/cpython/pull/27470/files -- ___ Python tracker ___

[issue41911] Language reference for expressions incorrectly specifies what type of object(s) are expected

Change by Andrei Kulakov : -- keywords: +patch nosy: +andrei.avk nosy_count: 3.0 -> 4.0 pull_requests: +25989 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27470 ___ Python tracker

[issue36643] Forward reference is not resolved by dataclasses.fields()

Eric V. Smith added the comment: Also, when dataclasses was originally written, it deliberately did not import typing, for performance reasons. I don't know if PEP 560 (I think) improved performance enough to make a difference. But adding this dependency needs to be looked at. But if we

[issue36643] Forward reference is not resolved by dataclasses.fields()

Eric V. Smith added the comment: I’m deferring any action on this until PEP 649 is ruled on. -- assignee: -> eric.smith ___ Python tracker ___

[issue36643] Forward reference is not resolved by dataclasses.fields()

Change by Misha Drachuk : -- keywords: +patch pull_requests: +25873 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27330 ___ Python tracker ___

[issue33063] failed to build _ctypes: undefined reference to `ffi_closure_FASTCALL'

Zachary Ware added the comment: The bundled version of libffi is no longer included in any version in bugfix support; closing this as out of date. As suggested in an earlier message, the libffi from your system should be used instead if you're building a version of Python that still

[issue33063] failed to build _ctypes: undefined reference to `ffi_closure_FASTCALL'

Change by Zachary Ware : -- pull_requests: -25844 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33063] failed to build _ctypes: undefined reference to `ffi_closure_FASTCALL'

santhosh added the comment: build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o: In function `ffi_prep_closure_loc': /opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.c:678: undefined reference to `ffi_closure_FASTCALL' /usr/bin/ld: build

[issue33063] failed to build _ctypes: undefined reference to `ffi_closure_FASTCALL'

Change by Fantix King : -- nosy: +fantix nosy_count: 3.0 -> 4.0 pull_requests: +25844 stage: -> patch review pull_request: https://github.com/python/cpython/pull/8620 ___ Python tracker

[issue36643] Forward reference is not resolved by dataclasses.fields()

Eric V. Smith added the comment: It can’t be resolved in fields(): it is still undefined when the fields are created. I think the best solution is PEP 649. -- ___ Python tracker

[issue44680] Reference cycles from a WeakKeyDictionary value to its key aren’t collected

Anders Kaseorg added the comment: > extra_states[o] = ExtraState(obj) (Typo for extra_states[obj] = ExtraState(obj), obviously.) -- ___ Python tracker ___

[issue44680] Reference cycles from a WeakKeyDictionary value to its key aren’t collected

New submission from Anders Kaseorg : Because WeakKeyDictionary unconditionally maintains strong references to its values, the garbage collector fails to collect a reference cycle from a WeakKeyDictionary value to its key. For example, the following program unexpectedly leaks memory: from

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

New submission from Vincent Bernat : asyncio will only keep weak references to alive tasks (in `_all_tasks`). If a user does not keep a reference to a task and the task is not currently executing or sleeping, the user may get "Task was destroyed but it is pending!". I would sugg

[issue36643] Forward reference is not resolved by dataclasses.fields()

Paolo Lammens added the comment: I was about to create the exact same ticket; I'm nudging this. -- nosy: +plammens ___ Python tracker ___

[issue7464] circular reference in HTTPResponse by urllib2

Irit Katriel added the comment: > It doesn't appear to be an issue in py3k. I agree, I can't find this code anywhere. Closing. -- nosy: +iritkatriel resolution: -> out of date stage: test needed -> resolved status: open -> closed ___ Python

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

STINNER Victor added the comment: Fix in the main branch: commit c10c2ec7a0e06975e8010c56c9c3270f8ea322ec Author: Antoine Pitrou Date: Fri May 14 21:37:20 2021 +0200 bpo-37788: Fix reference leak when Thread is never joined (GH-26103) When a Thread is not joined

[issue44192] Annotations, Inheritance and Circular Reference

Filipe Laíns added the comment: s/holder/older/ Sorry, my dyslexia is acting up. -- ___ Python tracker ___ ___ Python-bugs-list

[issue44192] Annotations, Inheritance and Circular Reference

Filipe Laíns added the comment: The annotations will effectively become strings, instead of object references, in Python 3.11, which solves this issue. You can enable this behavior in holder Python version with `from __future__ import annotations`, see PEP 563[1]. >>> class Base: ...

[issue44192] Annotations, Inheritance and Circular Reference

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

[issue44192] Annotations, Inheritance and Circular Reference

New submission from ReOb : Basically, I have: ``` class Base: _sub: list[Sub] class Sub: _parent: Base ``` What creates a circular reference. It could be solved doing: ``` class Sub: pass class Base: _sub: list[Sub] class Sub: _parent: Base ``` But in the annotation

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

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

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

miss-islington added the comment: New changeset b30b25b26663fb6070b8ed86fe3a20dcb557d05d by Antoine Pitrou in branch '3.9': [3.9] bpo-37788: Fix reference leak when Thread is never joined (GH-26103) (GH-26142) https://github.com/python/cpython/commit/b30b25b26663fb6070b8ed86fe3a20dcb557d05d

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

miss-islington added the comment: New changeset 71dca6ea73aaf215fafa094512e8c748248c16b0 by Miss Islington (bot) in branch '3.10': [3.10] bpo-37788: Fix reference leak when Thread is never joined (GH-26103) (GH-26138) https://github.com/python/cpython/commit

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Antoine Pitrou : -- pull_requests: +24777 pull_request: https://github.com/python/cpython/pull/26142 ___ Python tracker ___

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Antoine Pitrou : -- versions: -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by miss-islington : -- nosy: +miss-islington nosy_count: 14.0 -> 15.0 pull_requests: +24772 pull_request: https://github.com/python/cpython/pull/26138 ___ Python tracker

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Antoine Pitrou : -- nosy: +pitrou nosy_count: 13.0 -> 14.0 pull_requests: +24745 pull_request: https://github.com/python/cpython/pull/26103 ___ Python tracker ___

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Antoine Pitrou : -- versions: +Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Jesús Cea Avión added the comment: I retired the backporting request. Thanks, Ned. -- versions: -Python 3.6, Python 3.7 ___ Python tracker ___

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

hai shi added the comment: I created PR 25226. It's a another way to solve this problem. Compared to PR 15175, `_set_sentinel()` don't need to receive any params :) -- ___ Python tracker

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by hai shi : -- nosy: +shihai1991 nosy_count: 12.0 -> 13.0 pull_requests: +23963 pull_request: https://github.com/python/cpython/pull/25226 ___ Python tracker ___

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Martin Panter added the comment: Anselm's pull request PR 15175 looked hopeful to me. I've been using those changes in our builds at work for a while. -- ___ Python tracker

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Roundup Robot : -- nosy: +python-dev nosy_count: 11.0 -> 12.0 pull_requests: +23895 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/25148 ___ Python tracker

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

Raymond Hettinger added the comment: Thanks for the bug report. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.9 ___ Python tracker

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

Raymond Hettinger added the comment: New changeset d104a786fff5980360056d908a2d952b42306171 by Miss Islington (bot) in branch '3.9': bpo-43677: Fix a minor error in Doc/howto/descriptor.rst (GH-25123) (#25140) https://github.com/python/cpython/commit/d104a786fff5980360056d908a2d952b42306171

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

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

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

Raymond Hettinger added the comment: New changeset e689cdca3c14aab8d2d454b79ddd661b238fd301 by Zackery Spytz in branch 'master': bpo-43677: Fix a minor error in Doc/howto/descriptor.rst (#25123) https://github.com/python/cpython/commit/e689cdca3c14aab8d2d454b79ddd661b238fd301 --

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

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

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

Change by Zackery Spytz : -- keywords: +patch nosy: +ZackerySpytz nosy_count: 4.0 -> 5.0 pull_requests: +23870 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25123 ___ Python tracker

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

Eric V. Smith added the comment: I think it's PyMethod_Type. -- nosy: +eric.smith, rhettinger ___ Python tracker ___ ___

[issue43677] Descriptor.rst - Reference to Py_MethodType is not up to date

Change by Daniel Torres : -- title: Descriptor Documentation - Reference to Py_MethodType is not up to date -> Descriptor.rst - Reference to Py_MethodType is not up to date ___ Python tracker <https://bugs.python.org/issu

[issue43677] Descriptor Documentation - Reference to Py_MethodType is not up to date

Change by Daniel Torres : -- title: Documentation -> Descriptor Documentation - Reference to Py_MethodType is not up to date ___ Python tracker <https://bugs.python.org/issu

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Ned Deily added the comment: "Those releases are in their" -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Ned Deily added the comment: @jcea, I see you have created backports for 3.7 and 3.6 as well. Those release as in their security-fix-only phase of their life cycles. This doesn't seem like a security issue but am I missing something? -- nosy: +ned.deily

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Change by Jesús Cea Avión : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Jesús Cea Avión added the comment: New changeset d914813a7a9cee3b42e9c91f91ac491f3bbfe118 by Miss Islington (bot) in branch '3.9': bpo-35930: Raising an exception raised in a "future" instance will create reference cycles (GH-24995) (#25070) https://github.com/python/cpyt

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Jesús Cea Avión added the comment: New changeset dae1963cf38f730291126b7dadfda89ffb21cefd by Miss Islington (bot) in branch '3.8': bpo-35930: Raising an exception raised in a "future" instance will create reference cycles (GH-24995) (#25071) https://github.com/python/cpyt

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

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

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

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

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Jesús Cea Avión added the comment: New changeset 32430aadadf6e012e39167d3c18a24e49fb84874 by Jesús Cea in branch 'master': bpo-35930: Raising an exception raised in a "future" instance will create reference cycles (#24995) https://github.com/python/cpyt

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Change by miss-islington : -- nosy: +miss-islington nosy_count: 1.0 -> 2.0 pull_requests: +23820 pull_request: https://github.com/python/cpython/pull/25070 ___ Python tracker

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

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

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Jason R. Coombs added the comment: No. The issue remains open. -- stage: -> needs patch versions: -Python 3.7 ___ Python tracker ___

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Zhipeng Xie <775350...@qq.com> added the comment: ping I also encountered this problem. Is there a fix now? -- nosy: +Zhipeng Xie ___ Python tracker ___

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Change by Jesús Cea Avión : -- versions: +Python 3.10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Change by Jesús Cea Avión : -- assignee: -> jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Change by Jesús Cea Avión : -- keywords: +patch pull_requests: +23753 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24995 ___ Python tracker ___

[issue14189] C API documentation must document if returned object is a borrowed reference or strong reference

Irit Katriel added the comment: This was fixed for all the functions listed by the OP, except a few that no longer exist AFAICT: Doc/c-api/import.rst: _PyImport_FindExtension Doc/c-api/import.rst: _PyImport_FixupExtension Doc/c-api/init.rst: PyEval_GetCallStats Doc/c-api/int.rst:

[issue43533] Exception and contextmanager in __getattr__ causes reference cycle

New submission from Ran Chen : If __getattr__ raises exception within a contextlib.context_manager, it creates a reference cycle and prevents the frame from being garbage collected. This only happens if the exception is raised inside a context manager inside __getattr__. It doesn't happen

[issue40255] Fixing Copy on Writes from reference counting

Eric Snow added the comment: While the eventual solution may overlap, my interests are divergent enough from those here that I've created a separate issue: bpo-43503. -- ___ Python tracker

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

STINNER Victor added the comment: Oh, I'm confused. This issue is about the threading module, whereas bpo-37193 is unrelated: it's about the socketserver module. -- ___ Python tracker

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Mark Dickinson added the comment: Re-opening; I believe this issue is still valid. Here's output on a debug build on current master (commit 7591d9455eb37525c832da3d65e1a7b3e6dbf613) on my machine: lovelace:cpython mdickinson$ ./python.exe Python 3.10.0a6+

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Mark Dickinson added the comment: @Victor: How does the fix for #37193 solve this issue? I think I'm missing something. -- ___ Python tracker ___

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

STINNER Victor added the comment: bpo-37193 has been fixed. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue40255] Fixing Copy on Writes from reference counting

Eric Snow added the comment: Note that my PR does make the builtin types immortal (at least those initialized in _PyTypes_Init()). However, I did not make the singletons or other candidate objects immortal in the PR. That can be done separately. --

[issue40255] Fixing Copy on Writes from reference counting

Eric Snow added the comment: FYI, I've just put up a similar PR [1] to Eddie's, with a focus on object immortality rather than immutability. However, if Py_IMMORTAL_CONST_REFCOUNTS is defined then it should have the behavior Eddie is after. [1] https://github.com/python/cpython/pull/24828

[issue40255] Fixing Copy on Writes from reference counting

Change by Eric Snow : -- nosy: +eric.snow nosy_count: 15.0 -> 16.0 pull_requests: +23592 pull_request: https://github.com/python/cpython/pull/24828 ___ Python tracker ___

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43327] The docs falsely state that PyImport_ImportFrozenModuleObject() returns a new reference

Change by Zackery Spytz : -- keywords: +patch pull_requests: +23444 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24659 ___ Python tracker ___

[issue43327] The docs falsely state that PyImport_ImportFrozenModuleObject() returns a new reference

New submission from Zackery Spytz : The docs state that PyImport_ImportFrozenModuleObject() returns a new reference, but it actually returns an int. https://docs.python.org/3.10/c-api/import.html#c.PyImport_ImportFrozenModuleObject -- assignee: docs@python components: Documentation

[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

Change by Martin Panter : -- keywords: +3.7regression ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42824] get_type_hints throws for local class reference

Guido van Rossum added the comment: This is a known limitation. To get this to work you have to pass globals() and locals(): typing.get_type_hints(Test, globals(), locals()) -- nosy: +gvanrossum resolution: -> wont fix stage: -> resolved status: open -> closed

[issue42824] get_type_hints throws for local class reference

New submission from Fabian.M : The following code throws with "NameError: name 'Nested' is not defined". For reference, it works well when moving class definitions out of the local scope. import typing T = typing.TypeVar('T') def test(): class Nested(typing.Generic[T]):

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Change by Jesús Cea Avión : -- versions: +Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Jesús Cea Avión added the comment: Even more reproductible case, now 100%: """ import gc import concurrent.futures executor = concurrent.futures.ThreadPoolExecutor(999) def a(): 1/0 future=executor.submit(a) future.result() # An exception is raised here. That is normal del future #

[issue35930] Raising an exception raised in a "future" instance will create reference cycles

Jesús Cea Avión added the comment: The corrected test case in the terminal: (a "del" was missing) """ import gc import concurrent.futures executor = concurrent.futures.ThreadPoolExecutor(999) def a(): 1/0 future=executor.submit(a) future.result() # An exception is raised here. That is

[issue42482] TracebackException should not hold reference to the exception traceback

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

[issue42482] TracebackException should not hold reference to the exception traceback

miss-islington added the comment: New changeset 40b92f1cc06f9aaba813ae38266f424e0969b089 by Miss Islington (bot) in branch '3.9': [3.9] bpo-42482: remove reference to exc_traceback from TracebackException (GH-23531) (GH-23578) https://github.com/python/cpython/commit

[issue42262] [C API] Add Py_NewRef() function to get a new strong reference to an object

STINNER Victor added the comment: New changeset 8b6c4a921af6d5d0a9640211ac93d7886a55a8f3 by Victor Stinner in branch 'master': bpo-42262: Py_NewRef() casts its argument to PyObject* (GH-23626) https://github.com/python/cpython/commit/8b6c4a921af6d5d0a9640211ac93d7886a55a8f3 --

[issue42262] [C API] Add Py_NewRef() function to get a new strong reference to an object

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

[issue17852] Built-in module _io can lose data from buffered files in reference cycles

miss-islington added the comment: New changeset 4a44f53aa85c9400471ab084bc8fd8169065fc41 by Miss Islington (bot) in branch '3.9': [3.9] bpo-17852: Doc: Fix the tutorial about closing files (GH-23135) (GH-23527) https://github.com/python/cpython/commit/4a44f53aa85c9400471ab084bc8fd8169065fc41

[issue42482] TracebackException should not hold reference to the exception traceback

miss-islington added the comment: New changeset 1cc5c943c007b92116f06b3ec8e71f2a510d1898 by Miss Islington (bot) in branch '3.8': bpo-42482: remove reference to exc_traceback from TracebackException (GH-23531) https://github.com/python/cpython/commit/1cc5c943c007b92116f06b3ec8e71f2a510d1898

[issue42482] TracebackException should not hold reference to the exception traceback

miss-islington added the comment: New changeset 427613f005f0f412d12f0d775d2b609bae0ae1ad by Irit Katriel in branch 'master': bpo-42482: remove reference to exc_traceback from TracebackException (GH-23531) https://github.com/python/cpython/commit/427613f005f0f412d12f0d775d2b609bae0ae1ad

[issue42482] TracebackException should not hold reference to the exception traceback

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

[issue42482] TracebackException should not hold reference to the exception traceback

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

[issue42482] TracebackException should not hold reference to the exception traceback

Steven D'Aprano added the comment: Re-adding older versions. -- versions: +Python 3.8, Python 3.9 ___ Python tracker ___ ___

[issue42482] TracebackException should not hold reference to the exception traceback

Irit Katriel added the comment: I've added the refcount check that Victor suggested. -- ___ Python tracker ___ ___

[issue42482] TracebackException should not hold reference to the exception traceback

that no references are held, while still being able to fully print or format it. This issue shows that there was a bug in the implementation. -- The unit test should check the ref count of the exception and the exception traceback, to check functionally that no strong reference is hold

<    1   2   3   4   5   6   7   8   9   10   >