Expose PyInstaller.building.splash.Splash._check_tcl_tk_compatibility#15915
Merged
srittau merged 3 commits intoJun 15, 2026
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
…aller-expose-Splash._check_tcl_tk_compatibility
Contributor
|
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
srittau
approved these changes
Jun 15, 2026
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
2 participants
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.
As there's no current public API for this, I need to use a private method to pre-emptively test for Splash screen support without triggering a full PyInstaller build.
For a real-world example:
I've been using this for a while, but it was embedded in a build script until I moved my code to a proper Python module, where the type-checkers started screaming at me.