bndr / bndr/pycycle

Misses cycles not reachable from the first file found

Open
#9 1 comment 3 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
363
Forks
24
PR merge metrics
No merged PRs in 30d

Description

```console
$ echo import c > b.py
$ echo import b > c.py
$ ls
b.py c.py
$ pycycle --here
Project successfully transformed to AST, checking imports for cycles..
Cycle Found :(
b -> c: Line 1 =>> b
Finished.
$ touch a.py
$ ls
a.py b.py c.py
$ pycycle --here
Project successfully transformed to AST, checking imports for cycles..
No worries, no cycles here!
If you think some cycle was missed, please open an Issue on Github.
Finished.
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue with the shown b.py, c.py, and extra a.py files using pycycle --here. Start by tracing how the CLI chooses the first file and discovers imports; done means the b.py ↔ c.py cycle is reported whether or not a.py is present.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.