Open ns-ggeorgiev opened 11 months ago
Describe the bug When two or more packages share namespace, the tools seems to believe that all of the files in the namespace belong to one of the packages (it seems like the first one alphabetically)
To Reproduce Steps to reproduce the behavior:
Create two packages as described here: https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#pkgutil-style-namespace-packages
Create app that imports files from both
run the tool and observe the suggested list will not include one of the packages
Expected behavior All packages that have imports should be included.
Could you please provide an environment with the minimum requirements to reproduce this issue?
Describe the bug When two or more packages share namespace, the tools seems to believe that all of the files in the namespace belong to one of the packages (it seems like the first one alphabetically)
To Reproduce Steps to reproduce the behavior:
Create two packages as described here: https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#pkgutil-style-namespace-packages
Create app that imports files from both
run the tool and observe the suggested list will not include one of the packages
Expected behavior All packages that have imports should be included.