-
Notifications
You must be signed in to change notification settings - Fork 283
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
Fully adopt pathlib.PurePath for file paths #4523
Comments
Is this actually closable now @SimonPeatman @wjbenfold ? |
No, @pp-mo, this is the issue that has come out of the recent work on pathlib. We've so far introduced it "superficially" - i.e. the most frequently used bits of the public api will now accept a pathlib path but it's almost immediately converted to a string. This ticket is for the further work that would use paths all the way down (maybe converting input strings to paths) and leverage the features of paths that we currently use |
In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity. If this issue is still important to you, then please comment on this issue and the stale label will be removed. Otherwise this issue will be automatically closed in 28 days time. |
✨ Feature Request
Iris uses
os.path
to handle file paths, but the standard in Python 3 is to usepathlib.PurePath
objects. #3411 proposed adoptingpathlib.PurePath
and this is partially implemented by #3917. The present issue proposes replacingos.path
with the use ofpathlib
across the whole of Iris.Details
#3917 implements
pathlib.PurePath
for the main public functions only (load
,load_cube
,load_cubes
,load_raw
andsave
). See #3917 (review) for full details of what has been done and what is still to do.The text was updated successfully, but these errors were encountered: