On 8/10/2019 4:33 AM, Paul Moore wrote:
(Side issue)
This deserves its own thread.
As a Windows developer, who has seen far too many cases where use of slashes in filenames implies a Unix-based developer not thinking sufficiently about Windows compatibility, or where it leads to people hard coding '/' rather than using os.sep (or better, pathlib), I strongly object to this characterisation. Rather, I would simply say "to make Windows users more aware of the clash in usage between backslashes in filenames and backslashes as string escapes". There are *many* valid ways to write Windows pathnames in your code: 1. Raw strings 2. Doubling the backslashes 3. Using pathlib (possibly with slash as a directory separator, where it's explicitly noted as a portable option) 4. Using slashes IMO, using slashes is the *worst* of these. But this latter is a matter of opinion - I've no objection to others believing differently, but I *do* object to slashes being presented as the only option, or the recommended option without qualification.
Perhaps Python Setup and Usage, 3. Using Python on Windows, should have a section of file paths, at most x.y.z, so visible in the TOC listed by https://docs.python.org/3/using/index.html
-- Terry Jan Reedy _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/SH3M5GGHJPIMKVTEYI6FFBYWHVZT7O64/