-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Adding positional-only parameter notation (/
in function signature)
#2457
Adding positional-only parameter notation (/
in function signature)
#2457
Conversation
6b07492
to
23813a8
Compare
Just to surface it for you:
|
@Matiiss what's the status of this PR? Now that Python 3.7 has been dropped this should be able to move forward, once you fix the merge conflict. |
I had to read this sentence several times to understand it 😄 To do (I think):
|
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.
LGTM.
Don't think I've ever looked at so many forward slashes on one diff.
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.
Skimming over this it looks good, a good straightening out of our patterns to match modern conventions.
I am interested to make sure @ankith26 is okay with this approach before we merge.
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.
LGTM, thanks a lot for this PR 🎉
Closes #2445
TODO:
I'm planning on also removing type names from function signatures in the docs as that seems to be how positional-only parameters were notated before, also removing parentheses from function signatures in the docs, basically adopting positional-only parameter notation to its fullest extent.
Also haven't touched up on Python implementations and Cython (that one probably won't do at all?).
Some random notes (so I don't lose them):
A script I used for testing/checking that all functions that are implemented in C and don't accept keyword arguments are properly annotated in the stubs and docs (it's a bit of a mess).
The excluded doc names should be investigated further, most of them will get solved by changing what I mentioned above about general signature consistency and such.