David Seddon

I've found that I can get it down to one failing test with a couple of less-hacky feeling changes, see the commits on the end of [this draft PR](https://github.com/python/mypy/pull/16681/commits). The...

Thinking a bit more about it, such a contract could look like this: ``` [importlinter:contract:my-contract] name = My contract type = modular containers= mypackage ``` This would check that there...

> Ending the PR streak here Ha ha, thanks so much for all your work! It will take me a few days to go through everything, but excited to see...

Checking in on this. It's looking possible that my workplace will need something along these lines so I'm likely to have capacity to work on it if time is tight...

Thanks for this. There were a couple of issues raised https://github.com/seddonym/import-linter/issues/214 and https://github.com/seddonym/import-linter/issues/213, which made me wonder if we need to cover the problems raised by that other contributor. Any...

@QasimK as the original requester of this feature, would you mind taking a look and checking this meets your needs?

Thanks for the issue! I think you're right that the documentation is potentially confusing. When the [docs say](https://import-linter.readthedocs.io/en/stable/usage.html#top-level-configuration) this should contain 'the name of the Python package to validate', it's...

You should be able to fix this by adding pytest_check as one of the root packages. Alternatively, change `pytest_check.check` to just `pytest_check`. The reason for this is because Import Linter...

@pwalsh - I've opened a separate ticket for your question, see link above.

Interesting issue! As I understand it, what you're expecting to happen is that because Python executes the `__init__.py` of parents when importing a module, Import Linter should treat those as...