Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.1k
gh-109295: Clean up multiprocessing in test_asyncio and test_compileall#109298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
test_asyncio and test_compileall now clean up multiprocessing bycalling multiprocessing _cleanup_tests(): explicitly clean upresources and stop background processes like the resource tracker.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Gah. Why do we have compileall and py_compile in the stdlib. :-( (That's a rhetorical question.)
Thanks@vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
…mpileall (pythonGH-109298)test_asyncio and test_compileall now clean up multiprocessing bycalling multiprocessing _cleanup_tests(): explicitly clean upresources and stop background processes like the resource tracker.(cherry picked from commit09ea4b8)Co-authored-by: Victor Stinner <vstinner@python.org>
…mpileall (pythonGH-109298)test_asyncio and test_compileall now clean up multiprocessing bycalling multiprocessing _cleanup_tests(): explicitly clean upresources and stop background processes like the resource tracker.(cherry picked from commit09ea4b8)Co-authored-by: Victor Stinner <vstinner@python.org>
GH-109301 is a backport of this pull request to the3.12 branch. |
GH-109302 is a backport of this pull request to the3.11 branch. |
Well, why do we have asyncio and multiprocessing in the stlidb? Why do you have a stdlib? (That's a rhetorical question.) 😂 |
I would prefer that multiprocessing and concurrent.futures would have a more explicit API to manage resources. Rather than spawning processes in the background with no public API to be aware of that, nor an API to cleanup these processes. There are temporary directories, processes, shared memory, etc. Not trivial resources like a single large memory block. |
…ompileall (GH-109298) (#109302)gh-109295: Clean up multiprocessing in test_asyncio and test_compileall (GH-109298)test_asyncio and test_compileall now clean up multiprocessing bycalling multiprocessing _cleanup_tests(): explicitly clean upresources and stop background processes like the resource tracker.(cherry picked from commit09ea4b8)Co-authored-by: Victor Stinner <vstinner@python.org>
…ompileall (GH-109298) (#109301)gh-109295: Clean up multiprocessing in test_asyncio and test_compileall (GH-109298)test_asyncio and test_compileall now clean up multiprocessing bycalling multiprocessing _cleanup_tests(): explicitly clean upresources and stop background processes like the resource tracker.(cherry picked from commit09ea4b8)Co-authored-by: Victor Stinner <vstinner@python.org>
…mpileall (python#109298)test_asyncio and test_compileall now clean up multiprocessing bycalling multiprocessing _cleanup_tests(): explicitly clean upresources and stop background processes like the resource tracker.
Uh oh!
There was an error while loading.Please reload this page.
test_asyncio and test_compileall now clean up multiprocessing by calling _cleanup_tests() method: explicitly clean up resources and stop background processes like the resource tracker.