bpo-737999 Fix codeop.compile_command docstring by abenkovskii · Pull Request #3179 · python/cpython (original) (raw)
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 our terms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation9 Commits4 Checks0 Files changed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
codeop.compile_command actually accepts symbol="exec" too
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 we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons 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!
Fix codeop.compile_command docstring bpo-737999 Fix codeop.compile_command docstring
Hello! I can’t review right now, but wanted to say you might get more attention by opening a new doc bug instead of recycling an old ticket that’s already closed.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with Éric. @abenkovskii could you please open a new issue? bpo-737999 was closed 14 years ago so it would be better to discuss your ptahc in a new issue.
Also, we don't need a NEWS entry for this.
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.
@abenkovskii I agree with Berker, could you please open a new issue and remove the NEWS entry?
Closing as there hasn't been any response to multiple requests for a bug report to be opened. Please feel free to re-open this PR or create a new one to address the existing comments. Thanks!
@csabella Would you mind creating a doc ticket for this?