Migrate to using pathlib in most of the SDK #5435
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For user-facing functions, keep accepting
str
paths to maintain compatibility and flexibility, but add support for arbitrary path-like objects. For internal functions (indownloading.py
anduploading.py
), don't bother and requirepathlib.Path
.The only code that isn't converted is build-time code (e.g.
setup.py
) and code that came from openapi-generator.Motivation and context
pathlib
enables simpler, more type-safe code. This also makes the API more convenient for users who are already usingpathlib
(or an alternative path library).How has this been tested?
Unit tests.
Checklist
develop
branch[ ] I have updated the documentation accordingly[ ] I have added tests to cover my changes[ ] I have linked related issues (read github docs)[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,cvat-core, cvat-data and cvat-ui)
License
Feel free to contact the maintainers if that's a concern.