pyinstaller / pyinstaller/pyinstaller
Implement a "warning" mechanism for hooks
Open
Nobody has claimed this yet.
area:hooks
pull-request wanted
- Dominant language
- Python
- Stars
- 13.1k
- Forks
- 2k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
It would be useful, if hooks would issue warnings, e.g.
multiprocessing(and others) pointing to the respective recipe in the wikisslwarning about certificates need to be included- … more ideas
For this we could
- implement a simple logger in
utils.hookshaving a different output-format - think about not printing the the warnings of this hook immediately but collect them and print them at the end of the PyInstalelr run,
- suppress the output of this logger in while running the test-suite,
- add warnings to the resp. hooks (of course :-).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing hook mechanism in utils.hooks and how hooks run during the PyInstaller run and test suite. The issue proposes several possible warning designs, including collection and suppression, but does not select one. Done would require an agreed warning behavior, hook warnings, and corresponding handling in the test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100