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

[3.7] bpo-42406: Fix whichmodule() with multiprocessing (pythonGH-23403)#28489

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

Closed
faucct wants to merge1 commit intopython:3.7fromfaucct:patch-1

Conversation

faucct
Copy link

@faucctfaucct commentedSep 21, 2021
edited by bedevere-bot
Loading

We have hit this issue in 3.7 as well.

https://bugs.python.org/issue42406

drykovanov reacted with thumbs up emoji
@the-knights-who-say-ni

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed thePSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find abugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@faucct

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please followthe steps outlined in the CPython devguide to rectify this issue.

You cancheck yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

@ned-deily
Copy link
Member

Thanks for your PR. However,Python 3.7 has been in thesecurity-fix-only phase of its life cycle for over a year now so, unless it can be shown that this problem is security-related, it would not meet the criteria for a security-fix-only release.

@faucct
Copy link
Author

faucct commentedSep 23, 2021
edited
Loading

Can't this be merged now, but released whenever some security problem pops? This is not urgent for us, but we would like this to be fixed eventually.

@ned-deily
Copy link
Member

Sorry, I should have been clearer. Unless it is a security-related issue, it would not be a candidate to be merged into 3.7 at all, not just released.

@ned-deily
Copy link
Member

Since this does not seem to be a security issue for 3.7 as noted above, I am closing this PR. Sorry!

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@faucct@the-knights-who-say-ni@ned-deily@bedevere-bot

[8]ページ先頭

©2009-2025 Movatter.jp