Skip to content

bpo-32051: update multiprocessing doc - #4469

Merged
berkerpeksag merged 1 commit into
python:masterfrom
1a1a11a:master
Nov 27, 2017
Merged

bpo-32051: update multiprocessing doc#4469
berkerpeksag merged 1 commit into
python:masterfrom
1a1a11a:master

Conversation

@1a1a11a

@1a1a11a 1a1a11a commented Nov 19, 2017

Copy link
Copy Markdown
Contributor

Remove name conflict under "Using a remove manager" section, the original usage of queue conflicts with module name queue.

https://bugs.python.org/issue32051

@the-knights-who-say-ni

Copy link
Copy Markdown

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

Thanks again to your contribution and we look forward to looking at it!

@1a1a11a 1a1a11a changed the title Issue 32051 update multiprocessing doc [issue 32051] update multiprocessing doc Nov 19, 2017
@1a1a11a 1a1a11a changed the title [issue 32051] update multiprocessing doc bpo-32051: update multiprocessing doc Nov 19, 2017
@1a1a11a

1a1a11a commented Nov 19, 2017

Copy link
Copy Markdown
Contributor Author

I have signed the CLA, waiting for system to pass and re-check.

Comment thread Doc/library/multiprocessing.rst Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think multiprocessing.Queue is needed here. We don't communicate between different processes in the same machine so using queue.Queue is OK.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for the comment, what should I do now? Should I make the change and submit a new pull request?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't need to submit a new pull request. You can make the requested changes and push to your existing branch. In your case, that would be the master branch.

You can follow the guide at https://devguide.python.org/pullrequest/#step-by-step-guide for your future pull requests.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to add a NEWS entry for trivial documentation changes. Please delete this file.

@bedevere-bot

Copy link
Copy Markdown

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@1a1a11a 1a1a11a left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with this.

@1a1a11a

1a1a11a commented Nov 26, 2017

Copy link
Copy Markdown
Contributor Author

I have made the requested changes; please review again.

@bedevere-bot

Copy link
Copy Markdown

Thanks for making the requested changes!

@berkerpeksag: please review the changes made to this pull request.

Remove name conflict under "Using a remove manager" section
@1a1a11a 1a1a11a changed the title bpo-32051: update multiprocessing doc bpo-32051: update multiprocessing doc [skip news] Nov 27, 2017
@1a1a11a 1a1a11a changed the title bpo-32051: update multiprocessing doc [skip news] bpo-32051: update multiprocessing doc skip-news Nov 27, 2017
@1a1a11a 1a1a11a changed the title bpo-32051: update multiprocessing doc skip-news bpo-32051: update multiprocessing doc [skip-news] Nov 27, 2017
@1a1a11a

1a1a11a commented Nov 27, 2017

Copy link
Copy Markdown
Contributor Author

btw, how do I add skip news label?

@berkerpeksag berkerpeksag changed the title bpo-32051: update multiprocessing doc [skip-news] bpo-32051: update multiprocessing doc Nov 27, 2017
@miss-islington

Copy link
Copy Markdown
Contributor

Thanks @1a1a11a for the PR, and @berkerpeksag for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6.
🐍🍒⛏🤖

@bedevere-bot

Copy link
Copy Markdown

GH-4577 is a backport of this pull request to the 3.6 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Nov 27, 2017
@berkerpeksag

Copy link
Copy Markdown
Member

Thanks!

Labels can only be set by Python core developers or bots like bedevere.

berkerpeksag pushed a commit that referenced this pull request Nov 27, 2017
@1a1a11a

1a1a11a commented Nov 27, 2017

Copy link
Copy Markdown
Contributor Author

thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants