> On 11 May 2020, at 22:38, Andrew Barnert <abarn...@yahoo.com> wrote: > > On May 11, 2020, at 12:59, Barry Scott <ba...@barrys-emacs.org> wrote: >> >> >>> On 11 May 2020, at 18:09, Andrew Barnert via Python-ideas >>> <python-ideas@python.org <mailto:python-ideas@python.org>> wrote: >>> >>> More generally, what’s the use case for %-encoding filenames like this? Are >>> people expecting it to interact transparently with URLs, so if I save a >>> file “spam\0eggs” in a Python script and then try to browse to >>> file:///spam\0eggs <file:///spam/0eggs>” in a browser, the browser will >>> convert the \0 character to %00 the same way my Python script did and >>> therefore find the file? >> >> No. >> >> The \0 can never be part of a valid file in Unix, macOS or Windows. > > Of course. Which is exactly the kind of thing this sanitize function is meant > for. > > Hence my question: if my Python script is sanitizing all filenames with this > function with escape='%', is the expectation that it’ll actually give me > something that can be used if I paste the same thing into a browser and let > it url-escape a file URL? If so, will that actually work? If not, what _is_ > the intended use for this option? >
I misunderstood I thought you where saying that using escaping allowed bad chars to work. Barry
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/DVPYPFRO5PEJ6ELNMTQUSSYBYKHVIEWA/ Code of Conduct: http://python.org/psf/codeofconduct/
