[issue43719] Master build failure on Windows getting file system encoding

Pablo Galindo Salgado added the comment: Fixed by https://github.com/python/cpython/pull/25172 -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue43719] Master build failure on Windows getting file system encoding

Change by Terry J. Reedy : -- priority: normal -> critical ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43719] Master build failure on Windows getting file system encoding

Terry J. Reedy added the comment: Thanks everyone for the rapid responses. The PR fixes the build for me, with a clean test suite pass, so I added reviewers who could merge, a blurb, and my approval. This can be closed as out-of-date as soon as the (or a) fix is merged. --

[issue43719] Master build failure on Windows getting file system encoding

Dennis Sweeney added the comment: Correction: I opened GH-25172 -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue43719] Master build failure on Windows getting file system encoding

Dennis Sweeney added the comment: I could not successfully build even with deletion of __pycache__ in subfolders. I finally got the build to succeed after changing the magic number, so I opened GH-25069. -- ___ Python tracker

[issue43719] Master build failure on Windows getting file system encoding

David Bolen added the comment: Dennis, just to make sure I wasn't too literal, some of the __pycache__ folders are in subdirectories (at least in Tools), so just to double check, you did a recursive search beneath Tools and Parser right? -- ___

[issue43719] Master build failure on Windows getting file system encoding

Dennis Sweeney added the comment: I ran into the same issue on Windows 10 and git bisected it to the same first bad commit, fcb55c0037baab6f98f91ee38ce84b6f874f034a The issue persists after rm .\Parser\__pycache__\* My .\Tools directory has no __pycache__. -- nosy: +Dennis Sweeney

[issue43719] Master build failure on Windows getting file system encoding

David Bolen added the comment: Terry, it's not clear to me if this is the same issue (at first blush it appears different) but could you see if you have any pyc files in __pycache__ folders within the Tools or Parser directories in your tree that could be from prior builds? If so, remove

[issue43719] Master build failure on Windows getting file system encoding

STINNER Victor added the comment: IMO it's https://bugs.python.org/issue27129#msg389991 -- ___ Python tracker ___ ___

[issue43719] Master build failure on Windows getting file system encoding

Terry J. Reedy added the comment: Re ""f:\dev\3x\PC\validate_ucrtbase.py" ucrtbased" exited with co de -1073741819." f:\dev\3x>py -3.10 PC\validate_ucrtbase.py ucrtbased C:\WINDOWS\SYSTEM32\ucrtbased.DLL is version 10.0.14393.33 so the failure is due to running the file with the

[issue43719] Master build failure on Windows getting file system encoding

New submission from Terry J. Reedy : After a fresh update from upstream > PCbuild\build.bat -D (or without -D) on my machine ends with python.vcxproj -> f:\dev\3x\PCbuild\amd64\python_d.pdb (Full PDB) Python path configuration: PYTHONHOME = (not set) PYTHONPATH = 'f:\dev\3x\Lib'