Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
bpo-32126: Skip asyncio test when sem_open() is not functional#4559
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
| deftest_get_event_loop_new_process(self): | ||
| # Skip the test if the sem_open() implementation is broken. | ||
| support.import_module('multiprocessing.synchronize') |
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.
The check is very non-obvious.
Don't how to make it more verbose and explicit.
If it's impossible -- I can live with it.
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.
TheProcessPoolExecutor uses themultiprocessing (mp) module. Themp module is not functional when themp.synchronize module cannot be imported and all themp tests are skipped in that case. So we use here the same idiom used to skip themp tests (i.e.test.support.import_module('multiprocessing.synchronize')) to skip this test when the platformsem_open implementation is broken or missing.
What about replacing the comment with:
Issue bpo-32126: The multiprocessing module used by ProcessPoolExecutoris not functional when the multiprocessing.synchronize module cannot be imported.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.
New comment text is perfect!
Uh oh!
There was an error while loading.Please reload this page.
https://bugs.python.org/issue32126