Replies: 1 comment 3 replies
-
The "type printer" in Pyright doesn't include the full module path of a type. There is rarely any ambiguity, and the full module paths are verbose and hard to read, so we opted to use the short name always. Out of curiosity, why do you want the long names? Do you have a bunch of redundant class names in your project where the origin of the type isn't obvious from context? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to use reveal_type() directive to peek the type deduced by pyright. But it looks like pyright will only print the class name without the full "path" to that class.
For example, there's a directory structure like
and the ClassB.py:
When runnig:
in shell.
The output looks like this:
Is it possible to make the output like 'testProject.A.ClassB.ClassB', as the mypy did:
Beta Was this translation helpful? Give feedback.
All reactions