◐ Shell
clean mode source ↗

gh-74028: `concurrent.futures.Executor.map`: avoid reference cycles when an exception is raised by ebonnal · Pull Request #131701 · python/cpython

…le from failed future captured in its exception’s traceback

@ebonnal ebonnal changed the title test_concurrent_futures.test_map_exception: assert no reference cycle from failed future captured in its exception’s traceback test_concurrent_futures: Executor.map: assert no reference cycle from failed future captured in its exception’s traceback

Mar 25, 2025

@ebonnal ebonnal changed the title test_concurrent_futures: Executor.map: assert no reference cycle from failed future captured in its exception’s traceback concurrent.futures.Executor.map test: assert no reference cycle from failed future captured in its exception’s traceback

Mar 25, 2025

@ebonnal ebonnal changed the title concurrent.futures.Executor.map test: assert no reference cycle from failed future captured in its exception’s traceback concurrent.futures.Executor.map: test no reference cycle from failed future captured in its exception’s traceback

Mar 25, 2025

@picnixz picnixz changed the title concurrent.futures.Executor.map: test no reference cycle from failed future captured in its exception’s traceback gh-74028: concurrent.futures.Executor.map: test no reference cycle from failed future captured in its exception’s traceback

Mar 30, 2025

graingert

graingert

@ebonnal ebonnal changed the title gh-74028: concurrent.futures.Executor.map: test no reference cycle from failed future captured in its exception’s traceback gh-74028: concurrent.futures.Executor.map: test there are no reference cycles when an exception is raised

Mar 30, 2025
… to an Exception or a failed Future

@ebonnal

@graingert

@ebonnal ebonnal marked this pull request as ready for review

April 7, 2025 12:45

@ebonnal ebonnal changed the title gh-74028: concurrent.futures.Executor: avoid reference cycles when an exception is raised gh-74028: concurrent.futures.Executor.map: avoid reference cycles when an exception is raised

Apr 12, 2025

@ebonnal

kumaraditya303