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.
Miscellaneous smaller changes based on this week's issue tracker activity:
display version of
pyinstaller-hooks-contrib
next to PyInstaller version at program start, to make it easier to determine the user's actual setupwhen trying to run
pyinstaller
(or equivalentpython -m PyInstaller
) against non-existing script file(s), exit immediately - without trying to write the .spec file and building it. Mainly to avoid scenario with overwriting a customized .spec file due to typo in command's arguments (PyInstaller poiting to wrong spec file #8276), but also because I sometimes fail to change the directory prior to trying to build a test program, and then have to deal with stay .spec files.fix deprecation warnings emitted by
ruff
0.2.0bump the required
pyinstaller-hooks-contrib
version to the latest release, in attempt to minimize amount of issues reported due to old hooks.