pylyzer 0.0.47

A static code analyzer & language server for Python

pylyzer ⚡

pylyzer is a static code analyzer / language server for Python, written in Rust.

Installation

pip

pip install pylyzer

cargo (rust package manager)

cargo install pylyzer

build from source

git clone https://github.com/mtshiba/pylyzer.git
cargo install --path .

Make sure that cargo/rustc is up-to-date, as pylyzer may be written with the latest language features.

GitHub Releases

What is the advantage over pylint, pyright, pytype, etc.?

• Performance 🌟

On average, pylyzer can inspect Python scripts more than 100 times faster than pytype and pyright ¹. This is largely due to the fact that pylyzer is implemented in Rust.

• Detailed analysis 🩺

pylyzer can do more than the type checking. For example, it can detect out-of-bounds accesses to lists and accesses to nonexistent keys in dicts.

• Reports readability 📖

While pytype/pyright's error reports are illegible, pylyzer shows where the error occurred and provides clear error messages.

pylyzer 😃

pyright 🙃

• Rich LSP support 📝

pylyzer as a language server supports various features, such as completion and renaming (The language server is an adaptation of the Erg Language Server (ELS). For more information on the implemented features, please see here).

VSCode extension

You can install the VSCode extension from the Marketplace or from the command line:

code --install-extension pylyzer.pylyzer

What is the difference from Ruff?

Ruff, like pylyzer, is a static code analysis tool for Python written in Rust, but Ruff is a linter and pylyzer is a type checker & language server. pylyzer does not perform linting, and Ruff does not perform type checking.

How it works

pylyzer uses the type checker of the Erg programming language internally. This language is a transpiled language that targets Python, and has a static type system.

pylyzer converts Python ASTs to Erg ASTs and passes them to Erg's type checker. It then displays the results with appropriate modifications.

Limitations

• pylyzer's type inspector only assumes (potentially) statically typed code, so you cannot check any code uses reflections, such as exec, setattr, etc.

• pylyzer (= Erg's type system) has its own type declarations for the Python standard APIs. Typing of all APIs is not complete and may result in an error that such an API does not exist.

• Since pylyzer's type checking is conservative, you may encounter many (possibly false positive) errors. We are working on fixing this, but if you are concerned about editor errors, please turn off the diagnostics feature.

TODOs

• type checking
  • variable
  • operator
  • function/method
  • class
• type inference
  • variable
  • operator
  • function/method
  • class
• builtin modules resolving (partially)
• local scripts resolving
• local packages resolving
• collection types
  • list
  • dict
  • tuple
• typing
  • Union
  • Optional
  • Literal
  • Callable
  • TypedDict
  • type variable (TypeVar, Generic)
  • Protocol
  • Final
  • Annotated
  • TypeAlias
  • type guard (TypeGuard)
  • others
• collections.abc
  • Iterable
  • Iterator
  • Mapping
  • Sequence
  • others
• type assertion (typing.cast)
• type narrowing (is, isinstance)

---

¹ The performance test was conducted on MacBook (Early 2016) with 1.1 GHz Intel Core m3 processor and 8 GB 1867 MHz LPDDR3 memory.↩