-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Accepting pathlib.Path as path inputs? #5968
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
We don't do much in the way of path manipulations, and we do need to be On Thu, Feb 4, 2016 at 4:42 PM, K.-Michael Aye notifications@github.com
|
That was all I was dreaming of so that I don't have to do the casting all the time! ;) |
If you can come up with a list of functions that will need to do this On Fri, Feb 5, 2016 at 2:55 PM, K.-Michael Aye notifications@github.com
|
I will, just not this month, which looks like the busiest of my life… ;)
|
It's worth noting that there's now a path protocol outlined in https://www.python.org/dev/peps/pep-0519/. Using it you call os.fspath on a path to get a string/bytes view of the path, and the function is easy enough to backport (I've done this for h5py already). I'll try to submit a pull request in the next few days which adds this, should it be against master, or would this be small enough to the maintenance branches? |
Please target it at 2.x. |
Closed by #10231. |
I think this has regressed? I'm getting |
@LukeIreland1 Please open a new issue with your version details etc. |
pandas recently made the great effort to accept pathlib.Paths as inputs where traditionally strings would have to be provided for any path related requirements. Could this be done also for matplotlib?
The text was updated successfully, but these errors were encountered: