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-05-02.20:10:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> How about keeping a substitute or mapped drive from the input path
> if resolving the root path on the drive prefixes the overall real
> path? That would be pretty easy to implement.

So if the resolved path is accessible from the original path's drive, then keep the drive?
This is what 'realpath' in Ruby does. Good idea, in my opinion.
Letting this be default behavior (controlled by keyword argument) would prevent the issues with mounted drives.

> For your own needs, you could add a file that
> does "ntpath.realpath = ntpath.abspath". That will change the
> behaviour back to what it was in 3.7.

It works. Thank you very much.


Since you provided the working solution for me, the destiny of this bug report is at your discretion.
Date User Action Args
2021-05-02 20:10:57sfmcsetrecipients: + sfmc, paul.moore, tim.golden, zach.ware, eryksun, steve.dower
2021-05-02 20:10:57sfmcsetmessageid: <>
2021-05-02 20:10:57sfmclinkissue43968 messages
2021-05-02 20:10:57sfmccreate