-
-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
A few README tweaks #73
Conversation
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 is necessary for legal reasons before we can look at your contribution. Please follow these steps to help rectify the issue:
Thanks again to your contribution and we look forward to looking at it! |
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.
The copyright part of the PR is being discussed in #4. Rest of the PR looks good to me, thanks!
I just added my GitHub username in my bpo details. |
* Add a paragraph at the top for users, not builders, of Python. * Use nicer rst url syntax to avoid borking paragraphs in the plain text.
650797e
to
e6a6600
Compare
OK, removed the date changes. |
Codecov Report
@@ Coverage Diff @@
## master #73 +/- ##
==========================================
+ Coverage 82.37% 82.37% +<.01%
==========================================
Files 1427 1427
Lines 350948 350948
==========================================
+ Hits 289081 289089 +8
+ Misses 61867 61859 -8 Continue to review full report at Codecov.
|
Includes GH-2, pythonGH-70, pythonGH-73, and pythonGH-21.
…r-cursor Fix cursor position for double-width characters
Add a paragraph at the top for users, not builders, of Python.
No need to list every year individually. Use a range of years in the copyright.
Use nicer rst url syntax to avoid borking paragraphs in the plain text.