Is it possible to have a python package, that is defined in the source with a slightly unusual directory structure, be parsed so that PyCharm code navigation behaves desirably?
Because I’m mixing languages in my project, I’ve got an intermediate directory that ‘breaks’ what would be a clean package/module structure, which in turn prevents click-to-go-to-definition behavior from PyCharm. For example, the source for a package might be store like this:
module_c.py (<<< let’s say a function foo() is defined in this module)
[c++ files in this dir]
In any source that uses package_A, I might refer to a module like so:
from package_A.subpackageA_1.module_c import foo
My build process puts everything together so that this is correct and it runs properly in the “released” executable code, but this structure breaks code smarts in PyCharm (used during development) so that I can’t easily mouse-click on functions such as foo() and jump to the definition in module_c.
Is there a way to tweak some PyCharm setting - maybe something about project structure - that would allow this to behave properly? It *seems* like it might, hence my question!
Thanks in advance for any ideas...