Eryk Sun added the comment:
Where the POSIX specification uses the term "symbolic link" [1], it means one
and only one type of symlink, not multiple types of symlink with divergent
behavior depending on the context. To be consistent, only one type of Windows
reparse point [2] is classified a
Kagami Sascha Rosylight added the comment:
It seems libuv and pwsh decided to detect and read them just as symlinks:
https://github.com/libuv/libuv/pull/2812
https://github.com/PowerShell/PowerShell/pull/10331
Could Python do the same?
--
___
Pyth
Eryk Sun added the comment:
By design, appexec links (i.e. app execution aliases) cannot be followed
automatically. There is no handler for them in the kernel. WinAPI CreateFileW
fails with ERROR_CANT_ACCESS_FILE (1920), and the underlying NT status value is
STATUS_IO_REPARSE_TAG_NOT_HANDLED
New submission from Kagami Sascha Rosylight :
After installing Python from Microsoft Store, this fails:
```
>>> open('C:\\Users\\Kagami\\AppData\\Local\\Microsoft\\WindowsApps\\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\\python.exe')
Traceback (most recent call last):
File "", line 1,
