Here is a proposed addition to the tutorial noting the problem with using raw strings for windows paths and how to work around it.

Would it not be better to just recommend Windows users not to put that last backslash in at all? IIUC it's only needed to later append file names to directory names, but that's better achieved with os.path.join

Eli: Excellent and thoughtful point. This would indeed be exactly the place to suggest os.path.join as an alternative.

In addition, there are still occasions where one needs to form a string with trailing backslash. Two examples:

1. When writing the string specifying root directory: r'C:\ '[:-1]
2. Using python to prepare command lines to run other command line programs, where an argument may require a final backslash to explicitly specify a target directory (as opposed to a file).

I would rephrase:
+There is one subtle aspect to raw strings that is of special concern to Windows
+programmers: a raw string may not end in an odd number of \ characters.

to something like:
+There is one subtle aspect to raw strings: a raw string may not end in
+an odd number of \ characters. That is of special concern while
+dealing with Windows paths.

Otherwise it seems that this problem only affects raw strings on Windows.

Ezio Melotti ezio.melotti@gmail.com added the comment:

I would rephrase:
+There is one subtle aspect to raw strings that is of special concern to
Windows
+programmers: a raw string may not end in an odd number of \
characters.

to something like:
+There is one subtle aspect to raw strings: a raw string may not end in
+an odd number of \ characters. That is of special concern while
+dealing with Windows paths.

Otherwise it seems that this problem only affects raw strings on Windows.

I agree, but I'd also say something about os.path.join when mentioning
Windows paths, because the vast majority of problems that require the
trailing backslashes can be solved with it.

That would of course be a good addition too.

Well, the problem with both [:-1] and os.path.join is that they are inappropriate for that section of the tutorial. I considered putting the discussion later in the section so that I could use [:-1] (which hasn't been introduced at that point), but it made the flow even worse than adding the text where I did. I suppose the os.path.join could be put in if the sentence was short and cross referenced the library docs rather than going into a detailed example.

I'm on a quest to clear my 'commit ready' queue. This issue needs to go back to 'needs patch' stage...I'll leave it to someone else to rewrite my original patch based on the feedback, since it is unlikely I will get back to it any time soon. I'll commit it if someone else does the revision and moves it back to commit review, though ;)

The patch needs to be converted into a github PR, and modified according to the feedback on this issue.