-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
Stale Python Language Reference docs (no walrus). #84049
Comments
It looks like https://docs.python.org/3/reference/expressions.html and https://docs.python.org/3/reference/compound_stmts.html were never updated for named expressions. Because this change has to be backported, it's sort of a blocker for my PEP-614 doc updates in bpo-39702, which need to use the missing node in 3.9 only (I'd rather have this get a clean backport now than a messy one later)! Is somebody more familiar with PEP-572 willing to take this? Should be pretty straightforward. Pinging Emily since it looks like you've done some grammar/doc work for this in the past. |
Can I take this issue? |
Sorry, I hadn't seen your comment... :( I've already finished the grammar specification bit, but not the prose description of how assignment expressions work, etc. How about I leave that empty in my PR and you can actually do the documentation part afterward that's merged? Cool? I'd be happy to review it. |
Thank you for that!!! Can you please provide some pointers to what exactly I have to do? |
Of course. After my PR is merged, you can make another PR that replaces the ".. TODO: BPO-39868" line with a description of how assignment expressions work. Likely much of the language can be borrowed from the PEP. Let me know if you need help with any of the steps. Have you written RST / made a CPython PR on GitHub before? |
This is my first contribution to Python. This is why I am looking for some guidance, just point me to some resource, and then I will look into it thoroughly. I am reading this https://www.python.org/dev/peps/pep-0572/ for better understanding. |
Thanks for offering to help, Shankar! For this change, you can look at the other sections of the Doc/reference/expressions.rst file for an idea of what we're looking for. I think a few sentences and maybe a small code snippet should probably be fine. The devguide has all of the information that you need to get started. Specifically, you'll want to look at:
Also, you should sign the CLA *as soon as possible* (https://www.python.org/psf/contrib/contrib-form/)! Once you've made a PR, please request a review from me so I can make sure it moves along quickly. Let me know if you have any questions... I know it can be really tricky at first! |
Thank you for helping me out brandtbucher. As per my understanding, I am looking into the code (https://github.com/python/cpython/blob/master/Doc/reference/expressions.rst) and finding where the code doesn't follow the pattern described in (https://www.python.org/dev/peps/pep-0572/.) Please let me know if I am correct so that I will quickly go through everything and send you a pull request as soon as possible. |
I am also checking your commit for this: (8bae219) and see that you are changing the "expression: to "assignment_expression". Do I have to fill what assignment expression does with some examples? |
I got it that I have to fill the "Assignment expression" section in the code. I am working on it and send you the for review once I am done. |
Great. Just replacing the TODO line with your new description (and maybe an example) should be perfect! |
I have created my draft with an example but I am confused about where exactly do I have to add the code and push it. I have cloned these two repositories in my system and setup everything:
|
Great! It's not necessary to clone the devguide though; CPython is the only one you're going to edit. Make sure you've "forked" the repo on GitHub, and are working on a local clone of your fork. Otherwise things will be trickier.
Yes, you'll add the new documentation to line 1652, where the "TODO" comment is. You should make the changes in your own fork of the repo, and push. Then you'll be ready for a PR.
Working from master in your own fork is fine, but frequent contributors often prefer to branch from master and work on those branches instead. The pages I've linked to in the devguide walk you through every step of making a PR (including an intro on how to use Git). If it's easier for you, though, you can attach a copy of your edits to this issue and I can make a PR on your behalf. I just wouldn't count on repeating that workflow if you plan on contributing in the future; regular contributors should feel comfortable branching, committing, opening a PR, etc. |
I have added the pull request: #18851. Please check it out and let me know if I need to change anything. Thank you everyone for your guidance. |
Congratulations SHANKAR JHA. Thank you for your contribution. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: