Steve Dower added the comment:
Oh, and there's no harm in adding a note to that doc section explicitly
pointing out that it doesn't enable CPython itself to be installed to a long
path, and it may not enable packages to be imported from long paths in all
scenarios (as it's very feasible
Steve Dower added the comment:
It enables it for accessing from within Python, but doesn't enable Python
itself to be installed into a long path. And because a venv is essentially an
installation, they're included in that. (Possibly %PYTHONPATH% entries are too.)
I haven't checked how
schwaerz added the comment:
I see.
Reading
https://docs.python.domainunion.de/3/using/windows.html#removing-the-max-path-limitation
I thought that the long paths on Win10 are supposed to be supported in general.
Is there any blocker in particular which I should keep in mind?
--
Eryk Sun added the comment:
The secure CRT string functions such as wcscpy_s() and wcscat_s() invoke the
invalid parameter handler if the destination string is too small. This defaults
to a fastfail that terminates with the status code 0xC409, subcode 5
(FAST_FAIL_INVALID_ARG).
We're
New submission from schwaerz :
When trying to create a venv from within a long path name in Windows 10 (long
paths enabled in the registry), python crashes. Used python 3.9.6.
When reducing the path length by one character, it starts working.
When disabling the long path support in Windows, I
