After learning about TYPE_CHECKING i made it a habit to put all imports that were only needed for type checking into an if TYPE_CHECKING: guard. But now I am wondering if that is actually intended to be used like that. Checking whether an import is only needed at type checking time can get quite tedious and sometimes you run into situations were you introduced some code that made the import a requirement at runtime.
How do you use TYPE_CHECKING? Whenever it is possible or only when using it actually solves a circular import?
You should have part of your test harness perform a separate import of every module. If your module is idempotent (most good code is) you could do this in a single process by cleaning
sys.modulesI guess … but it still won’t be part of yourpytestprocess.Static analyzers can only detect some cases, so can’t be fully trusted.
I’ve also found there are a lot of cases where performant Python code has to be implemented in a distinct way from what the type-checker sees. You can do this with aggressive
type: ignorebut I often find it cleaner to use separateifblocks.