branch analysis
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 190
- Avg merge
- 8m
- Merged PRs (30d)
- 13
Description
I'm creating this mostly as a duplicate target
pyflakes currently does not do any branch analysis and as such can't really know when things are conditionally defined / undefined / dead code / etc.
doing accurate branch analysis is a hard problem and often requires some amount of dynamic analysis so it is unlikely pyflakes will ever actually implement this
there are better alternatives which attempt to do this such as type checkers (mypy, pyright) and to some extent pylint
Contributor guide
No contributing guide indexed for this repository
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 issue body and its statement that branch analysis is unlikely to be implemented in pyflakes. The issue names no files, tests, entry points, or concrete acceptance criteria; it points to mypy, pyright, and pylint as alternatives, so no defined completion condition is provided.
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
- 5/100