➜

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 sfmc
Recipients eryksun, paul.moore, sfmc, steve.dower, tim.golden, zach.ware
Date 2021-04-30.08:20:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1619770804.45.0.914163296524.issue43968@roundup.psfhosted.org>
In-reply-to
Content 
I see the point: the real path may not be accessible from the substitute drive:
 - if symlink (or junction) is used, pointing to path not visible from the substitute drive.
 - if different security context is used (e.g. different user or UAC).

But that is the discussion about the _correct_ behavior (which may have differing opinions if the exact behavior is not documented).

-----

Let's discuss how we can fix the issue caused by the behavior change.

I propose a simple fix: keep old behavior if a special environment variable is specified.

E.g. if you specify env. var. PYTHON_NTREALPATH_OLD_BEHAVIOR=1, it doesn't resolve symlinks and junctions.

Is this acceptable for Python 3.8.10?
History
Date User Action Args
2021-04-30 08:20:04sfmcsetrecipients: + sfmc, paul.moore, tim.golden, zach.ware, eryksun, steve.dower
2021-04-30 08:20:04sfmcsetmessageid: <1619770804.45.0.914163296524.issue43968@roundup.psfhosted.org>
2021-04-30 08:20:04sfmclinkissue43968 messages
2021-04-30 08:20:04sfmccreate