David Seddon

Hi and thanks for the issue request! Offhand I would have thought this already works, but happy to consider a PR for this!

> Looking at your code reveals that your fields use CharFields. They do indeed! Sounds like you sorted out your issue?

The key is probably to allow any of the methods that return sets of modules to also allow client code to see the import paths for these modules. With the...

Hi @brahn, thanks for looking into this. I haven't looked into this in detail yet but a few initial thoughts: - Running Import Linter can take significant time, depending on...

> The new API method would ideally provide access to the violations as structured data. We do already have a type for this - it's called a [ContractCheck](https://github.com/seddonym/import-linter/blob/dd61468901ea04c241d80d04a4d972ad8b00b439/src/importlinter/domain/contract.py#L100). Those checks...

Gentle bump on this - I see the teardown function was included a year ago but there hasn't been a release since then. It would be great to be able...

Thanks!

Thanks for the issue! Could I clarify what you're expecting to happen? E.g. are you expecting the `lint-imports` command to behave differently, or do you want the command not to...

> it probably will be too many imports to add to ignore_imports Ignored imports supports wildcards, so you would probably be able to achieve it with just a single line...

Agreed. Perhaps the simplest way to do this would be to support passing in a regular expression, something like: `impulse drawgraph mypackage --exclude=^mypackage\.foo*` Happy to consider a pull request for...