[issue38931] pathlib.Path on Windows - parser issue

Zachary Ware added the comment: You're welcome :) -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue38931] pathlib.Path on Windows - parser issue

tempest added the comment: But for course! (Slaps forehead!) Yes, giving the Windows path as a raw string works. For all the times I've done '\t'.join(str(f) for f in some_array) to get a tab-delimited text string, I should have had a clue. Sorry for the noise, and thanks for setting me

[issue38931] pathlib.Path on Windows - parser issue

Zachary Ware added the comment: Note that you're using backslashes in a non-raw string; in particular, you're naming your file `\x09est.eps`. Try `Path(r'C:\Temp\MyProj.wc\test.eps')` and see if that works for you. -- ___ Python tracker

[issue38931] pathlib.Path on Windows - parser issue

Change by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38931] pathlib.Path on Windows - parser issue

New submission from tempest : the Path parser from pathlib seems to give incorrect paths if a folder (subdirectory) name includes a period. (This issue does not manifest with Unix paths.) Please see a demonstration below: "Out[2]" is not the same as "Out[3]" and "Out[4]"; the "\" separator