validate_filename() and sanitize_filename() pass '.' and '..' about pathvalidate HOT 4 CLOSED

pathvalidate v3.2.0 can do the following:

from pathvalidate import sanitize_filename, ValidationError

def add_trailing_underscore(e: ValidationError) -> str:
    if e.reusable_name:
        return e.reserved_name

    return f"{e.reserved_name}_"

sanitize_filename(".", reserved_name_handler=add_trailing_underscore, additional_reserved_names=["."])

'._'

from pathvalidate.

Was this ever resolved? I have the same issue in 2.5.2

It would be great if sanitize_filename("..") (or maybe sanitize_filename("..", check_reserved=True)) returned "_"

from pathvalidate.

I have considered this previously and concluded that it is difficult to apply replacements unconditionally.
Unlike other reserved words, . and .. can be assumed to be recognized as reserved keywords and used as reserved names in most cases, so I think it is inappropriate to treat them in the same way as other reserved words.
In many cases, users would expect to preserve . and .. as they are, and there is a possibility that the valid file paths are broken if they are replaced.

In the future, another solution may be to add an interface that specifies a callback function to process reserved names.
By customizing this callback function, changing the behavior as you wish will be possible.

from pathvalidate.

In many cases, users would expect to preserve . and .. as they are, and there is a possibility that the valid file paths are broken if they are replaced.

I agree that they probably shouldn't be replaced in sanitize_filepath since both . and .. are valid in relative paths. But personally I'm not sure I would expect them to ever be valid via sanitize_filename since you cannot name a file . or ...

I suppose if people are using sanitize_filename to check individual path components then they might want to preserve periods.

from pathvalidate.