This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.j3
Recipients 888xray999, paul.j3, rhettinger
Date 2020-03-05.20:33:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1583440393.62.0.706349546766.issue39845@roundup.psfhosted.org>
In-reply-to
Content
Then this isn't an argparse issue.  Probably not even a Python one.  The windows shell (which one? cmd.exe?  power? some batch) is making the substitution. 

I see lots of discussion about Windows use of backslash, both as directory separator and escape.  None seems to exactly apply.

For your application the use of a custom 'type' function might well be appropriate, but it's not something we want to add to argparse.  It's a user specific patch.
History
Date User Action Args
2020-03-05 20:33:13paul.j3setrecipients: + paul.j3, rhettinger, 888xray999
2020-03-05 20:33:13paul.j3setmessageid: <1583440393.62.0.706349546766.issue39845@roundup.psfhosted.org>
2020-03-05 20:33:13paul.j3linkissue39845 messages
2020-03-05 20:33:13paul.j3create