-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
absolute path bug #16
Comments
Thank you for your report. This behavior is expected. |
Thank you for your comment although it does not seem to be about my report. The question is to sanitize a path, not to create it. Moreover, under Unix, Linux, FreeBSD, etc., paths can be created independently of being absolute or relative. (Only file/directory permissions matter.) In addition, if an absolute path may be problematic for some platforms (certainly not for Linux), |
I mean, create a sanitized file path by
In
There is a reason. shell-reserved characters like vertical line ( |
Whereas
sanitize_filepath
works perfectly for a relative path, it has an unexpected behaviour on absolute paths. It either rises an exception or, whenplatform
is specified as 'auto' or 'Linux', it lefts the string unchanged.The execution (see sanitize-filepath-bug.pdf) has been run with Python 3.8.5 under Linux (Ubuntu 20.04.2 LTS). I've just installed for the first time
pathvalidate
today via pip.The text was updated successfully, but these errors were encountered: