[issue46171] venv module produces spurious warning that location has moved

Eryk Sun added the comment: > My VHDX mounted in a directory is affected by this I created a VHDX and mounted it in a directory. It's just a regular volume mount point with a junction (IO_REPARSE_TAG_MOUNT_POINT). That won't cause any problems, so I guess your setup must be different in some

[issue46171] venv module produces spurious warning that location has moved

Steve Dower added the comment: My VHDX mounted in a directory is affected by this, and actually broke a couple of tools until I also mounted it as a drive. (Using a VHDX helps bypass a lot of filesystem related perf impacts on Windows, so it's worth the occasional broken tool.) I suspect (b

[issue46171] venv module produces spurious warning that location has moved

Eryk Sun added the comment: > There are plenty of other ways to get a venv through a potentially > unexpected path (turns out I've been doing one for years) Examples would be appreciated because I'm drawing a blank here. A junction or directory symlink in the parent path shouldn't be a probl

[issue46171] venv module produces spurious warning that location has moved

Steve Dower added the comment: There are plenty of other ways to get a venv through a potentially unexpected path (turns out I've been doing one for years), which is why I went with the general warning rather than limiting it to specific behaviours that are subject to change outside of our c

[issue46171] venv module produces spurious warning that location has moved

Change by Filipe Laíns : -- nosy: +FFY00 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue46171] venv module produces spurious warning that location has moved

Eryk Sun added the comment: There's still the problem of the system using short names in %TEMP%, since by default that's under "%USERPROFILE%\AppData". Either an exception could be made for the temp directory, since it's never redirected (AFAIK), or support could be added for GetLongPathName

[issue46171] venv module produces spurious warning that location has moved

Eryk Sun added the comment: There's no point to making the user worry about short names, symlinks, or non-canonical mount points in the filesystem path of a virtual environment. It's still accessible where the user expects to find it. The problem for bpo-45337 is filesystem redirection in UW

[issue46171] venv module produces spurious warning that location has moved

New submission from layday : After https://github.com/python/cpython/commit/6811fdaec825bd6ab64e358a4b480108f5634d2d the venv module produces spurious warnings for venv paths which contain DOS-encoded parts e.g. "USER\~1" in "C:\Users\USER~1". `tempfile.gettempdir()` returns legacy paths like t