You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a problem, because Microsoft's Pylance extension for VSCode uses this repo for the source of its bundled Django stubs. As a result, if I enable type checking in a modern Django project (Django 5.0.x), I get a lot of erroneous type errors, such as this:
yeah stubs will fall behind, I only added things that I've needed when I've need them rather than trying to keep 1:1 with Django
for instance, in my django project I don't use admin so there wasn't any admin definitions, but someone else needed them so they added them to this project
The stubs in this repo are considerably out of date with upstream. This can be seen clearly in https://github.com/sbdchd/django-types/blob/main/django-stubs/utils/deprecation.pyi, where I see this snippet:
Compare with the head of upstream:
This is a problem, because Microsoft's Pylance extension for VSCode uses this repo for the source of its bundled Django stubs. As a result, if I enable type checking in a modern Django project (Django 5.0.x), I get a lot of erroneous type errors, such as this:
I reported this as an issue in Pylance (microsoft/pylance-release#6029) and they directed me to you.
The text was updated successfully, but these errors were encountered: