Replies: 2 comments 3 replies
-
|
Can you mock up a repo that demonstrates this? There are potentially many moving parts, and it's hard to know what exactly is going on without seeing them all in action |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
How do you reproduce the mypy issue you're having? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm facing a configuration problem with Pants + mypy in a monorepo.
I’m trying to keep a monorepo layout. The problem arises when executing:
I have set mypy to use django-stubs for type checking inside of django_project, but the Django-specific mypy configuration is being applied to all Python targets including pure_python. This causes errors such as:
because pure_python obviously has no Django settings module. I want Django type-checking with django-stubs only for django_project/. However MyPy seems to apply plugin config globally. This makes non-Django packages fail pants check.
Is there a recommended way to scope mypy configuration to only certain targets / source roots so that Django settings aren't required for unrelated packages?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions