[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Steve Dower added the comment: Marking this as fixed, because the fix is already checked in. Release scheduling is a separate conversation, so keep an eye out for the next release. -- resolution: -> fixed stage: -> resolved status: open -> closed ___

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Steve Dower added the comment: Oh I think I know what happened. Because RT_MANIFEST wasn't defined, it was added as a resource tagged with that as a string. So the manifest is still embedded, just not under the right type constant, so it has no effect. Yeah, I think we should do a fresh rele

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Eryk Sun added the comment: > How are you checking whether it's there or not? The desktop distribution of 3.9.8 is the most obvious case, since it causes sys.getwindowsversion() to report Windows 8.0 (6.2.9200): C:\Temp>"C:\Program Files\Python39\python.exe" -q >>> import sys >>>

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Steve Dower added the comment: > I just installed it and can confirm that there's no embedded manifest in > "C:\Program > Files\WindowApps\PythonSoftwareFoundation.Python.3.9<...>\python.exe". Strange, because when I inspect the files that I published, it's there. It's also in the version t

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Eryk Sun added the comment: > Did my accidental breakage of the resource files make it > into the last 3.9 release? Yep, version 3.9.8 of the store app was built last Friday, the day after removing "winuser.h" from the resource definition files. I just installed it and can confirm that ther

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Steve Dower added the comment: > Did my accidental breakage of the resource files make it into the last 3.9 > release? Turns out, no, it didn't. So this is something else. When I get to work later today I'll take a look. -- ___ Python tracker

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Abdullah Alnajim added the comment: LongPathsEnabled value was already one. This issue comes with the new update (3.9.8) [Windows Store version]. I reinstalled the same version (3.9.8) from Windows Store, and the issue was still there. When I tried versions (3.10) and (3.9.7) from (https://w

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Steve Dower added the comment: Oh, no, wait. Did my accidental breakage of the resource files make it into the last 3.9 release? If so, we probably lost the manifest option to opt-in to supporting long paths, and perhaps Windows 11 has decided to start honouring that (Windows 10 ignored it).

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Steve Dower added the comment: I wonder if the Windows 11 upgrade process disables this registry key when it's set directly? That's not something we can fix (I don't think?), so we may just have to list it as an option. If you can, check whether running a Repair of your Python install offer

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Eryk Sun added the comment: Ensure that the system has LongPathsEnabled set to 1. For example, in PowerShell with administrator (elevated) access: PS C:\> $p = "HKLM:\System\CurrentControlSet\Control\Filesystem" PS C:\> get-itempropertyvalue $p LongPathsEnabled 0 It was set to 0,

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

Change by Eric V. Smith : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___ P

[issue45777] Issue in reading files with a path longer than 256 letters after latest update

New submission from Abdullah Alnajim : After updating python to the latest version, an issue related to reading files in long paths (>256 letters) is arisen. Whenever I try to read such a file in Windows 11, I got an exception telling me that the file is not there, even though it’s there and I