pyright VS ruff

is used with the type checkers such as mypy, pyright, pyre-check, pytype, etc.

mypy (and pyright occasionally) as a type checker,

They identified this as a bug and fixed it, then changed course and decided to reinstate the behaviour. So if you want to write idiomatic Python, you need to disable typechecking TypedDicts.

— https://github.com/microsoft/pyright/issues/1739

Now if this were a linter then I would understand. But a type checker should not be opinionated to the point of pushing people not to use idiomatic Python.

Pyright:

This is a good summary: https://github.com/microsoft/pyright/blob/main/docs/mypy-com...

But without that, I always felt like I was actively fighting mypy. It seemed like it was written for a totally different language than Python.

Compared to another more modern type system like TypeScript, sometimes you don't explicitly type something and yet TypeScript usually does exactly what you expect.

We have it already: https://github.com/microsoft/pyright

Python (pyright)

Pyright is billed as a "static type checker" but its a full-blown language server (which pylance is built on). I've used both pylance and pyright and frankly I haven't seen any benefit going up to pylance. Pyright is under the MIT license so it can be used for anything: https://github.com/microsoft/pyright/blob/main/LICENSE.txt

There was a hang/performance bug [1, 2] that was reported just after the beta release, which we've since fixed [3]. You might try seeing if we get through your entire project now?

(And as an aside, there _is_ a verbose mode: if you add `-vv` you'll get DEBUG-level log messages printing out the name of each file as we start to check it, and you can set TY_MAX_PARALLELISM=1 in your env to make it very clear which file is causing the hang. That's how we debug these kinds of issues when they're reported to us.)

[1] https://github.com/astral-sh/ty/issues/1968

[2] https://github.com/astral-sh/ty/issues/1993

[3] https://github.com/astral-sh/ruff/pull/22030

Ruff Documentation

To begin with, I created a ci.yml file that runs on push and pull request to the main branch. The workflow has two major jobs. The first is the test job, which runs on a matrix of Ubuntu, Windows, and macOS to ensure cross-platform reliability. It checks out the repository, sets up Python 3.12 with pip caching, installs all necessary dependencies, runs linting and formatting checks using ruff, performs type checking with mypy(static type checker for Python), and finally executes the full test suite with coverage reporting. The second job is a build job that runs only if the tests pass successfully. It installs the build tools, creates distribution packages using python -m build, and uploads the generated artifacts so they can be reviewed.

ruff Description: An extremely fast Python linter and code formatter, written in Rust. What we like: Orders of magnitude faster than other Python linters, very active development. What we don't like: Still a zero-point release (0.14 as of this article), which allows for breaking changes in minor and patch releases.

Let's start the conversation on how to 'measure' maintainable, and architecturally sound Python code. And keep Goodhart's law: "When a measure becomes a target, it ceases to be a good measure" in mind ;-)

The wise path is the one that avoids the shell entirely when not needed. Most linters (like ruff) will detect this for you.

I am also looking forward to uv, the really fast Python package manager written in Rust. I think Rust tooling for Python has great potential. Astral is also making a project called Ruff, which is a formatter and I'm also very excited about that.

Ruff: A Rust-based, ultra-fast Python linter and formatter developed by Astral (official website). What's astounding is not just its speed, but its ability to cover most of the checks and formatting previously done by multiple tools like Flake8, isort, pydocstyle, pyupgrade, etc., with Ruff alone. This simplifies configuration files and significantly reduces tool management costs. Ruff hooks are defined in .pre-commit-config.yaml. When you try to commit, static code analysis (detecting potential bugs or deprecated practices) and formatting (unifying coding style) are automatically executed. If issues are found, the commit is aborted, prompting you to fix them. In many cases, Ruff can automatically fix the problems it finds.