> But first, it should be stopped by any of several > standard precautions. For example, applying os.path.realpath (come to > think of it, PEP 383 should say something about realpath, shouldn't > it?)
Why do you think so? I think the existing documentation of realpath is correct and complete. > and os.path.normpath (PEP 383 should definitely say something > about this function Precisely what? > maybe PEP 3131 should, too) How can this be of relevance? > > Nothing is lost at the moment. > > Nothing is lost compared to 'strict', true, but under the PEP as it is > a large fraction of Shift JIS and Big5 filenames cannot be read under > ASCII-compatible file system encodings using 'utf8b'. Yet it is those > users who are placed at risk by PEP 383. I think this statement is incorrect. Those filenames *can* be read just fine. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com