Use pathlib.Path for file path handling #514
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for this! We've included this in the next-gen project (v4). We'll make sure to credit you for the contribution. 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR changes all file and directory path handling to use
pathlib.Pathinstead of using strings andos.pathfunctions. The initial reason for this is that simply prepending"file://"to the path of the report does not generate a valid URI on Windows, where the directory separator is\, because you end up with something likefile://D:\proj\report.html, which uses backslashes, and file URIs are supposed to use forward slashes. Instead we can use thepathlib.Path.as_uri()function to get a valid URI. While I was at it, I changed the rest of the file[s] to usepathlib.Pathas well.