➜
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.
Created on 2018-08-14 15:04 by Alisue Lambda, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (6) | |||
|---|---|---|---|
| msg323527 - (view) | Author: Alisue Lambda (Alisue Lambda) | Date: 2018-08-14 15:04 | |
https://docs.python.org/3.8/using/windows.html#removing-the-max-path-limitation Current > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem@LongPathsEnabled Should be > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled |
|||
| msg323534 - (view) | Author: Pablo Galindo Salgado (pablogsal) *  |
Date: 2018-08-14 19:11 | |
Isn't this saying that LongPathsEnabled is a value on the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem? |
|||
| msg323535 - (view) | Author: Pablo Galindo Salgado (pablogsal) * |
Date: 2018-08-14 19:12 | |
I am not sure how people usually refer to the Windows register but this seems that the current line is differentiating from the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem and the value LongPathsEnabled |
|||
| msg323550 - (view) | Author: Ammar Askar (ammar2) * |
Date: 2018-08-15 06:57 | |
For what its worth, window's reg command also makes a distinction between the registry key and value:
C:\Users\ammar>reg.exe QUERY HKLM\Software\Microsoft\.NETFramework\Enable64Bit
ERROR: The system was unable to find the specified registry key or value.
C:\Users\ammar>reg.exe QUERY HKLM\Software\Microsoft\.NETFramework /V Enable64Bit
HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework
Enable64Bit REG_DWORD 0x1
Maybe it can just be phrased as something like, "set the registry value LongPathsEnabled in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem"
|
|||
| msg323566 - (view) | Author: Steve Dower (steve.dower) * |
Date: 2018-08-15 13:31 | |
Yeah, it definitely shouldn't be a backslash there. The @ isn't my invention, but last time someone questioned it I couldn't find any public examples, so it may be an internal Microsoft thing? I'm not totally attached to it, but if you want to fix it it'll need to be written out in full that it's "a value named X of type Y". |
|||
| msg415629 - (view) | Author: Irit Katriel (iritkatriel) * |
Date: 2022-03-20 19:48 | |
This has been fixed by now. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:04 | admin | set | github: 78587 |
| 2022-03-20 19:48:04 | iritkatriel | set | status: open -> closed nosy: + iritkatriel messages: + msg415629 resolution: out of date stage: resolved |
| 2018-08-15 13:31:13 | steve.dower | set | messages: + msg323566 |
| 2018-08-15 07:51:48 | berker.peksag | set | nosy:
+ steve.dower |
| 2018-08-15 06:57:55 | ammar2 | set | nosy:
+ ammar2 messages: + msg323550 |
| 2018-08-14 19:12:54 | pablogsal | set | messages: + msg323535 |
| 2018-08-14 19:11:41 | pablogsal | set | nosy:
+ pablogsal messages: + msg323534 |
| 2018-08-14 15:04:57 | Alisue Lambda | set | title: Type in documentation -> Typo in documentation |
| 2018-08-14 15:04:48 | Alisue Lambda | create | |