-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
Follow PEP-8 guidelines in tutorial for standard library #26127
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 and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow PEP-8 guidelines in tutorial for standard library #26127
Conversation
In the original PR (25288), which this PR replaces, I asked several questions, including: 1. The checks complain that "skip issue" and skip news" labels are miissing. How do I add labels? 2. What does it mean for the checks to report that required checks have been skipped. 3. I have examined the logs from the "Docs PR - Build documentation" pre-build check. What does this error mean, and what was I supposed to have done to avoid it? ``` 2021-04-08T22:28:01.3554327Z Warning, treated as error: 2021-04-08T22:28:01.3556468Z /home/vsts/work/1/s/Doc/using/configure.rst:416:unknown option: --enable-universalsdk 2021-04-08T22:28:03.8447865Z Makefile:49: recipe for target 'build' failed 2021-04-08T22:28:03.8481903Z make: *** [build] Error 2 2021-04-08T22:28:03.8538418Z ##[error]Bash exited with code '2'. ``` All of my questions were ignored. This PR ran into some of the same failures. I tried to correct the missing "skip news" label by clicking on the "Details" link, which took me to a page where I was asked to register my GitHub account with a tool called "blurb_it" which in turn presented me with a form asking for an issue number and a PR number. There is no issue number, as my understanding is that for some PRs (such as minor documentation corrections) it is inappropriate to create a GitHub issue. Nevertheless, the form requires that the issue number field not be left blank, so I entered "none" and submitted the form again, and it was accepted. Now, however, the PR build is failing with the following error message: ``` ValueError: invalid literal for int() with base 10: 'none' ``` So I am removing the news file to eliminate this error. It would be awesome if I could get some answers to the questions above.
In my last commit message, I wrote "... inappropriate to create a GitHub issue" where I should have written "... inappropriate to create a b.p.o. issue." |
This PR is stale because it has been open for 30 days with no activity. |
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.
Since this is in the tutorial, I think it's fine to make this change. I did a quick look at that page (though no other ones in the tutorial), and this is the only such case.
Thanks @bkline for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10. |
GH-32294 is a backport of this pull request to the 3.10 branch. |
GH-32295 is a backport of this pull request to the 3.9 branch. |
) (cherry picked from commit 6db2db9) Co-authored-by: Bob Kline <bkline@users.noreply.github.com>
) (cherry picked from commit 6db2db9) Co-authored-by: Bob Kline <bkline@users.noreply.github.com>
According to PEP-8, "Arguments on first line forbidden when not using vertical alignment."
No ticket created in b.p.o., as this is a trivial documentation change.
My understanding from reading other tickets related to PEP-8 compliance in the documentation (for example, https://bugs.python.org/issue26030) is that PRs should be submitted as users come across violations of the PEP. If my understanding is wrong, please let me know.