bndr / bndr/pycycle

not detecting various imports and missing cycles

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

Description

Hi,
it seems the tool doesn't process all the import syntax correctly. Not sure which ones it skips but I recommend checking into it:

import Package [as newname]
from Package import sub [as newname]
from .. import relativething [as newname]
from Foo import *

I don't know if the cycle detection is buggy or that the tool misses some imports (or both), but it doesn't find any cycle at all in my [Pyro4 ](https://github.com/irmen/Pyro4) project. But there sure are cycles! See https://github.com/irmen/Pyro4/issues/148 (the graphs are generated by my own cycle analisys tool + graphviz btw)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by running the tool against the Pyro4 project and compare its results with the cycle graphs referenced in Pyro4 issue #148. Investigate handling of the listed import forms, including aliases, relative imports, and wildcard imports. Done means these imports are processed correctly and the known Pyro4 cycles are detected.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.