Repository navigation
Conversation
…ion modules Windows can't load a DLL with an embedded manifest from a path near MAX_PATH, even with long paths enabled, so python.exe failed to start from long paths. The manifest has no effect in a DLL. The executables keep theirs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
All commit authors signed the Contributor License Agreement. |
Author
|
This also should be backported to all stable branches, most likely. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The way that CPython compiles DLLs for Windows causes an unnecessary problem with long paths (#160624).
This removes the manifest, and the
RT_MANIFESTfallback define that only it used, fromPC/python_nt.rcandPC/sqlite3.rc. That coverspython3XY.dll,python3.dll,sqlite3.dll, and every extension module.python.exe,pythonw.exe, and the launchers keep theirs.