Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Merged
xdegaye merged 2 commits intopython:masterfromxdegaye:bpo-32126
Nov 26, 2017
Merged

bpo-32126: Skip asyncio test when sem_open() is not functional#4559

xdegaye merged 2 commits intopython:masterfromxdegaye:bpo-32126
Nov 26, 2017

Conversation

@xdegaye
Copy link
Contributor

@xdegayexdegaye commentedNov 25, 2017
edited by bedevere-bot
Loading


deftest_get_event_loop_new_process(self):
# Skip the test if the sem_open() implementation is broken.
support.import_module('multiprocessing.synchronize')
Copy link
Contributor

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.

Copy link
ContributorAuthor

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.

Copy link
Contributor

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!

@xdegayexdegaye merged commita6fba9b intopython:masterNov 26, 2017
@xdegayexdegaye deleted the bpo-32126 branchNovember 26, 2017 09:31
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@asvetlovasvetlovasvetlov left review comments

@1st11st1Awaiting requested review from 1st1

Assignees

No one assigned

Labels

testsTests in the Lib/test dirtopic-asyncio

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@xdegaye@asvetlov@the-knights-who-say-ni@bedevere-bot

[8]ページ先頭

©2009-2025 Movatter.jp