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 steve.dower
Recipients Mo, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-10-25.20:06:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572034008.38.0.812525276293.issue38583@roundup.psfhosted.org>
In-reply-to
Content
I agree this would be better, though it may not be that easy to do.

If you're running Windows Python from WSL, then your "bash style" path should be "/mnt/c/some/path", not "/c/some/path". So the answer isn't as simple as .replace('\\', '/').

I did some quick testing with posixpath and pathlib and neither has an obvious conversion from a Windows path to a POSIX path, though pathlib.PurePosixPath(pathlib.PureWindowsPath(p)) comes closest.

Perhaps the best approach here is to improve `activate` to determine its path when run, like we did for `activate.ps1`? Then we don't need to substitute the path in at creation time.
History
Date User Action Args
2019-10-25 20:06:48steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, Mo
2019-10-25 20:06:48steve.dowersetmessageid: <1572034008.38.0.812525276293.issue38583@roundup.psfhosted.org>
2019-10-25 20:06:48steve.dowerlinkissue38583 messages
2019-10-25 20:06:48steve.dowercreate