Message285301
I opened issue 29248 for the os.readlink bug and issue 29250 for the inconsistency between os.path.islink and os.stat.
Handling junctions as links is new behavior, so I've changed this issue to be an enhancement for 3.7.
If the notion of a link is generalized to junctions, then maybe it should be further generalized to include all name-surrogate reparse tags [1]. Currently for Microsoft tags this includes
IO_REPARSE_TAG_MOUNT_POINT (junctions)
IO_REPARSE_TAG_SYMLINK
IO_REPARSE_TAG_IIS_CACHE
For non-Microsoft tags it includes
IO_REPARSE_TAG_SOLUTIONSOFT
IO_REPARSE_TAG_OSR_SAMPLE
IO_REPARSE_TAG_QI_TECH_HSM
IO_REPARSE_TAG_MAXISCALE_HSM
The last two are outliers. HSM isn't the kind of immediate, fast access that one would expect from a symbolic link. All other HSM tags aren't categorized as name surrogates.
[1]: https://msdn.microsoft.com/en-us/library/aa365511 |
|
Date |
User |
Action |
Args |
2017-01-12 10:52:28 | eryksun | set | recipients:
+ eryksun, tim.golden, craigh, zach.ware, steve.dower, eric.fahlgren |
2017-01-12 10:52:28 | eryksun | set | messageid: <1484218348.77.0.417232344925.issue23407@psf.upfronthosting.co.za> |
2017-01-12 10:52:28 | eryksun | link | issue23407 messages |
2017-01-12 10:52:28 | eryksun | create | |
|