django-stubs
pyright
django-stubs | pyright | |
---|---|---|
7 | 135 | |
1,462 | 12,098 | |
1.8% | 1.8% | |
9.6 | 9.8 | |
3 days ago | 3 days ago | |
Python | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-stubs
-
Mypy 1.6 Released
Pyright doesn't work with Django, as Django's so dynamic that it requires a plugin to infer all types correctly. Sadly, even mypy with plugins is a mess to get set up in vscode, especially if you want it to use the same config as you use for ci checks from the command line.
We use mypy + [django-stubs](https://github.com/typeddjango/django-stubs) (in a huge Django + drf project at day job) which includes a plugin for mypy allowing it to recognize all reverse relations and manager methods. Mypy is still really rough around the edges. The cli args are poorly documented, and how they correspond to declarations in a mypy.ini / pyproject.toml is mysterious. Match-statements still have bugs even a year after release. Exclusion of untyped / partially typed files and packages we've had to solve with grep filtering mypy's output for our whitelisted set of files, as it's been unable to separate properly between errors you care about (in your own codebase) and errors in others code (dependencies, untypable dynamic python packages etc).
The largest issue IMO is that mypy tried to adapt a java / OOP style way of type system onto python, instead of recognizing the language's real power within duck typing and passing structural types around. Typescript chose the right approach here, modelling javascript the way it is actually written, favoring structural over nominal typing, instead of the archaic and now left-behind way of Java-style OOP that has influenced mypy.
There was a recently accepted PEP which allowed for limited dataclass transforms, enough to cover the @attr.s usecase for both mypy and pyright, but nowhere near expressive enough to cover django's models and ORM sadly. It's probably impossible / undesirable to allow for such rich plugins, so i see the future for proper pluginless typing to be more akin to how pydantic / normal dataclasses solve typing, by starting with a specification of the types, deriving its runtime implementation, instead of plugins having to reverse the type representation of a custom DSL.
-
Boring Python: Code Quality
You can annotate the manager and get some typing help in the editor. And there’s django-stubs which helps a little when running mypy. It’s not as good as pycharm though.
https://github.com/typeddjango/django-stubs/tree/master
-
Python 3.11.0 final is now available
> Yes, there are type stubs for these libraries but they’re either forced to be more strict, preventing use of dynamism, or opt for being less strict but allowing you to use all the library features, at the cost of safety.
There are type stubs for Django that somewhat avoid these compromises: https://github.com/typeddjango/django-stubs
To be able to do this they have to use a Mypy plugin though. And even then it's still far from perfect.
- Welcome to hassle free coding
-
Is Rust Web Yet?
Mypy together with this plug-in gives you typing for django. https://github.com/TypedDjango/django-stubs
-
Django projects with type hints?
Have you looked at stubs for Django?
- Neovim + Django - LSP config
pyright
-
Enhance Your Project Quality with These Top Python Libraries
Pyright is a fast type checker meant for large Python source bases. It can run in a “watch” mode and performs fast incremental updates when files are modified.
-
How to speed up Pyright + eglot.
However, I made it faster for my use-case by changing some settings. Neovim allows to have these settings in the setup function for LSP. I was trying to figure out how do I change these settings with doom emacs. Pyright docs suggest to have these settings in pyrightconfig.json.
-
Mypy 1.6 Released
Not exactly what you are looking for but maybe useful to others.
https://github.com/microsoft/pyright/blob/main/docs/mypy-com...
-
VSCodium – Libre Open Source Software Binaries of VS Code
You can use pyright instead[0]. It is the FOSS version of pyright, but having some features missing.
[0]: https://github.com/microsoft/pyright
-
How do you enable semantic highlighting for Python?
Unfortunately, pyright explicitly stated that they are not interested in inlay hints or other language server features, that those will only be added to pylance. That's why I added it myself instead of submitting a pull request to pyright. See https://github.com/microsoft/pyright/issues/4325
-
How do I enable an LSP for json files?
return { -- add pyright to lspconfig { "neovim/nvim-lspconfig", ---@class PluginLspOpts opts = { ---@type lspconfig.options servers = { -- Listed servers will be automatically loaded to buffers jsonls = { settings = { json = { format = { enable = true, }, }, validate = { enable = true }, }, }, pyright = { settings = { python = { analysis = { -- https://github.com/microsoft/pyright/blob/main/docs/settings.md autoSearchPaths = false, useLibraryCodeForTypes = true, diagnosticMode = "openFilesOnly", }, }, }, }, }, -- Add folding capability to use LSP for ufo plugin capabilities = { textDocument = { foldingRange = { dynamicRegistration = false, lineFoldingOnly = true, }, }, }, }, }, }
-
VSCode isn't Recognizing installed Python Modules?
[{ "resource": "/Documents/Coding/VSCode/Projects/Photoeditor/PhotoEditor.py", "owner": "_generated_diagnostic_collection_name_#0", "code": { "value": "reportMissingModuleSource", "target": { "$mid": 1, "external": "https://github.com/microsoft/pyright/blob/main/docs/configuration.md#reportMissingModuleSource", "path": "/microsoft/pyright/blob/main/docs/configuration.md", "scheme": "https", "authority": "github.com", "fragment": "reportMissingModuleSource" } }, "severity": 4, "message": "Import \"requests\" could not be resolved from source", "source": "Pylance", "startLineNumber": 2, "startColumn": 8, "endLineNumber": 2, "endColumn": 16 }]
-
Pyright does not respect virtualenv (astronvim)
I don't use astro, but you can configure pyright by using a pyrightconfig.json or directly in the LSP configuration.
- Eglot + pyright can not get completion on django.db.models
-
Remote Development, Python IDE.
I prefer jedi over pyright as pyright has crippled documentation support outside of VSCode. I also found jedi is make correct suggestions based on inferred type in some situations where pyright would need type annotation to provide completions, pyright is significantly faster though. Jedi with mypy and flake8 is comparable to pyright I think, but unfortunately mypy wasn't working over tramp. Also isort wasn't working over tramp, but jedi, black, importmagic and flake8 all worked.
What are some alternatives?
strawberry - A GraphQL library for Python that leverages type annotations 🍓
jedi-language-server - A Python language server exclusively for Jedi. If Jedi supports it well, this language server should too.
phantom-types - Phantom types for Python.
mypy - Optional static typing for Python
pandas-stubs - Pandas type stubs. Helps you type-check your code.
python-lsp-server - Fork of the python-language-server project, maintained by the Spyder IDE team and the community
lagom - 📦 Autowiring dependency injection container for python 3
python-language-server - Microsoft Language Server for Python
pandas-stubs - Public type stubs for pandas
coc-jedi - coc.nvim wrapper for https://github.com/pappasam/jedi-language-server
returns - Make your functions return something meaningful, typed, and safe!
pylance-release - Documentation and issues for Pylance