-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
FIX make dataset fetchers accept os.Pathlike
for data_home
#27468
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
FIX make dataset fetchers accept os.Pathlike
for data_home
#27468
Conversation
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 on my side. Thanks @Charlie-XIAO
@adrinjalali do you want to have a look.
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.
Happy to merge, since this was supported already anyway. But I'm not sure if we really support ANY pathlike object though.
…t-learn#27468) Co-authored-by: Guillaume Lemaitre <g.lemaitre58@gmail.com>
…t-learn#27468) Co-authored-by: Guillaume Lemaitre <g.lemaitre58@gmail.com>
Co-authored-by: Guillaume Lemaitre <g.lemaitre58@gmail.com>
…t-learn#27468) Co-authored-by: Guillaume Lemaitre <g.lemaitre58@gmail.com>
Reference Issues/PRs
Fixes #27447.
What does this implement/fix? Explain your changes.
This PR changes the parameter constraints of the dataset fetchers from
[str, None]
to[str, os.PathLike, None]
.Any other comments?
The functions do have the ability to handle
os.PathLike
, but previouslyvalidate_params
is disabling it. The unit test also only makes sure that it is able to handle thesedata_home
, but does check explicitly for each data fetcher. Not sure if this is sufficient.