Closed bwildenborg closed 3 months ago
Actually, it appears to be related to include_external_packages = True with the namespace package. Once turned on, I get the error even if there are no external packages in the contracts.
Thanks for your bug report!
I'm unable to reproduce the problem though. What directory are you running lint imports from?
Looks like this was an issue with some otherwise benign import cycles. Poor way to surface the error, but it looks like more of an issue with how grimp surfaces the error rather than import-linter.
Hello, I have a namespace package, and when I try to use a forbidden contract with import-linter 2.0 I get an error:
I cut out all of my code, so my namespace package is effectively just:
Where init.py is empty. My .importlinter file looks like:
If I switch this to a standard package and update the config to refer to ns instead of ns.one, it works as expected.