-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
[SPRINT] Functions with *args can now have explicit keyword args #17345
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
Comments
It turns out this specific case is fixed by #17324. Are there others? |
Other others are:
|
Can I work on this for the June 6th Sprint? I can do all three or just take one if other participants want to work on the others. If I take one, I'll take shuffle. It sounds like I would add random_state, and n_samples as keyword args. If this is available, just let me know whether I should only do shuffle or can take all three. |
@JosephTLucas Let's do |
Take |
Take CC: @cemeiqra |
Take shuffle |
all of the issues are taken here for now. (Although there may be more that I have not found) |
We are already working on shuffle with @JosephTLucas . |
There was one more than I missed: |
I'll take a jab at |
Yup you can work on this. |
Uh oh!
There was an error while loading. Please reload this page.
Please do not address this issue unless you're part of the sprint (June 6th 2020).
Functions like
resample
have a signature likedef resample(*arrays, **options)
because of a limitation of python 2, where named keyword arguments could not be used with variable number of positional argument. We now should be using explicit keyword arguments where possible.The text was updated successfully, but these errors were encountered: