false detection of cyclic dependencies when using mypy about pydeps HOT 3 OPEN

You can globally remove the dependency on the command line by adding -x some_module or you can add it to a .pydeps file at the root of your project (check pydeps' own .pydeps file for syntax: https://github.com/thebjorn/pydeps/blob/master/.pydeps).

There is currently no way to only ignore some_module, but only for filename foo.py.

You can export the dependency graph as json with the --show-deps flag (it's a very simple format and it should be much easier to work with than removing/adding types to the source files), but there is unfortunately not a way to give a json dependency graph to pydeps for display..

from pydeps.

@thebjorn I think in cases where the imports under if TYPE_CHECKING are of the same package that we are trying to check, excluding it doesn't work. Is there any way to have pydeps not take into account imports under if TYPE_CHECKING?

from pydeps.

@skroth pydeps (and Python's modulefinder) doesn't do any semantic analysis, i.e. it only scans the .pyc files for opcodes related to imports, so unfortunately there is no way to check if-opcodes when they are generated(*).

(*) in Python I'm only aware of one case where the if is eliminated by the optimizer, and that is if <boolean-constant>:. This is py3+ only, since True and False became real constants in the language. Maybe that can solve your question (see https://discuss.python.org/t/moving-type-checking-out-of-typing-and-into-the-built-in-namespace/7870)

from pydeps.