Files

Brent Westbrook a9efdea113 Use ast::PythonVersion internally in the formatter and linter (#16170 )

## Summary

This PR updates the formatter and linter to use the `PythonVersion`
struct from the `ruff_python_ast` crate internally. While this doesn't
remove the need for the `linter::PythonVersion` enum, it does remove the
`formatter::PythonVersion` enum and limits the use in the linter to
deserializing from CLI arguments and config files and moves most of the
remaining methods to the `ast::PythonVersion` struct.

## Test Plan

Existing tests, with some inputs and outputs updated to reflect the new
(de)serialization format. I think these are test-specific and shouldn't
affect any external (de)serialization.

---------

Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>

2025-02-18 12:03:13 -05:00

benches

Use ast::PythonVersion internally in the formatter and linter (#16170 )

2025-02-18 12:03:13 -05:00

resources

Vendor benchmark test files (#15878 )

2025-02-02 18:16:07 +00:00

src

Vendor benchmark test files (#15878 )

2025-02-02 18:16:07 +00:00

Cargo.toml

Move red_knot_python_semantic::PythonVersion to the ruff_python_ast crate (#16147 )

2025-02-14 12:48:08 -05:00

README.md

Update contributing docs to use cargo bench -p ruff_benchmark (#9535 )

2024-01-15 14:57:30 -05:00

README.md

Ruff Benchmarks

The ruff_benchmark crate benchmarks the linter and the formatter on individual files:

# Run once on the "baseline".
cargo bench -p ruff_benchmark -- --save-baseline=main

# Compare against the "baseline".
cargo bench -p ruff_benchmark -- --baseline=main

# Run the lexer benchmarks.
cargo bench -p ruff_benchmark lexer -- --baseline=main

See CONTRIBUTING.md on how to use these benchmarks.