ruff/crates/red_knot
Matthew Mckee cdafd8e32b
Allow discovery of venv in VIRTUAL_ENV env variable (#16853)
## Summary

Fixes #16744 

Allows the cli to find a virtual environment from the VIRTUAL_ENV
environment variable if no `--python` is set

## Test Plan

Manual testing, of:
- Virtual environments explicitly activated using `source .venv/bin/activate`
- Virtual environments implicilty activated via `uv run`
- Broken virtual environments with no `pyvenv.cfg` file
2025-03-20 13:55:35 +00:00
..
docs [red-knot] Add mypy_primer usage documentation (#16679) 2025-03-12 16:47:10 +01:00
src Allow discovery of venv in VIRTUAL_ENV env variable (#16853) 2025-03-20 13:55:35 +00:00
tests red_knot: update diagnostic output snapshots 2025-03-17 12:46:49 -04:00
Cargo.toml [red-knot] Add argfile and windows glob path support (#16353) 2025-02-25 08:43:13 +01:00
README.md Add `red_knot/README.md` (#16230) 2025-02-18 23:31:02 -08:00
build.rs [red-knot] Add version command (#15823) 2025-02-02 18:56:51 +00:00

README.md

Red Knot

Red Knot is an extremely fast type checker. Currently, it is a work-in-progress and not ready for user testing.

Red Knot is designed to prioritize good type inference, even in unannotated code, and aims to avoid false positives.

While Red Knot will produce similar results to mypy and pyright on many codebases, 100% compatibility with these tools is a non-goal. On some codebases, Red Knot's design decisions lead to different outcomes than you would get from running one of these more established tools.

Contributing

Core type checking tests are written as Markdown code blocks. They can be found in red_knot_python_semantic/resources/mdtest. See red_knot_test/README.md for more information on the test framework itself.

The list of open issues can be found here.