Summary
Track refreshing the third-party type stubs that Pylance bundles (starting with Django) so they better match recent package versions, and/or provide a supported way to disable/override the bundled stubs.
Background
Split out from #6029. Bundled Django stubs (sourced from sbdchd/django-types) have lagged behind recent Django releases, producing false is unknown import symbol errors for symbols that exist in the installed package (for example RemovedInDjango51Warning).
Documented workaround for users today: override the bundled stubs with a workspace-local partial stub package via python.analysis.stubPath. See How to Override Bundled Third-Party Stubs in Pylance.
Asks raised by users
- Ship fresher bundled stubs (Django in particular).
- Evaluate switching the Django stub source (for example
typeddjango/django-stubs, which has added pyright support).
- Consider an option to disable bundled third-party stubs.
Related
Summary
Track refreshing the third-party type stubs that Pylance bundles (starting with Django) so they better match recent package versions, and/or provide a supported way to disable/override the bundled stubs.
Background
Split out from #6029. Bundled Django stubs (sourced from
sbdchd/django-types) have lagged behind recent Django releases, producing falseis unknown import symbolerrors for symbols that exist in the installed package (for exampleRemovedInDjango51Warning).Documented workaround for users today: override the bundled stubs with a workspace-local partial stub package via
python.analysis.stubPath. See How to Override Bundled Third-Party Stubs in Pylance.Asks raised by users
typeddjango/django-stubs, which has added pyright support).Related