➜

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 eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-08-14.22:23:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565821421.25.0.273013351915.issue37834@roundup.psfhosted.org>
In-reply-to
Content 
> Perhaps the best we can do is an additional test where we GetFinalPathName, strip the prefix, reopen the file, GetFinalPathName again and if they match then return it without the prefix. That should handle the both long path settings as transparently as we can.

I tried this and the downside (other than hitting the filesystem a few more times) is that any unresolvable path is going to come back with the prefix - e.g. symlink cycles and dangling links.

Maybe that's okay? The paths are going to be as valid as they can get (that is, unusable :) ) and it at least means that long paths and deliberately unnormalized paths.

Posted an update to PR 15287 with that change.
History
Date User Action Args
2019-08-14 22:23:41steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun
2019-08-14 22:23:41steve.dowersetmessageid: <1565821421.25.0.273013351915.issue37834@roundup.psfhosted.org>
2019-08-14 22:23:41steve.dowerlinkissue37834 messages
2019-08-14 22:23:41steve.dowercreate