Fix minor punctuation errors (#16228)

Co-authored-by: eqsdxr <rxdsqe@gmail.com>
This commit is contained in:
Alex Waygood 2025-02-18 12:24:57 +00:00 committed by GitHub
parent ed9c18d9b4
commit 5cd0de3e4c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 7 additions and 7 deletions

View file

@ -209,8 +209,8 @@ This change only affects those using Ruff under its default rule set. Users that
### Remove support for emoji identifiers ([#7212](https://github.com/astral-sh/ruff/pull/7212)) ### Remove support for emoji identifiers ([#7212](https://github.com/astral-sh/ruff/pull/7212))
Previously, Ruff supported the non-standard compliant emoji identifiers e.g. `📦 = 1`. Previously, Ruff supported non-standards-compliant emoji identifiers such as `📦 = 1`.
We decided to remove this non-standard language extension, and Ruff now reports syntax errors for emoji identifiers in your code, the same as CPython. We decided to remove this non-standard language extension. Ruff now reports syntax errors for invalid emoji identifiers in your code, the same as CPython.
### Improved GitLab fingerprints ([#7203](https://github.com/astral-sh/ruff/pull/7203)) ### Improved GitLab fingerprints ([#7203](https://github.com/astral-sh/ruff/pull/7203))

View file

@ -526,7 +526,7 @@ cargo benchmark
#### Benchmark-driven Development #### Benchmark-driven Development
Ruff uses [Criterion.rs](https://bheisler.github.io/criterion.rs/book/) for benchmarks. You can use Ruff uses [Criterion.rs](https://bheisler.github.io/criterion.rs/book/) for benchmarks. You can use
`--save-baseline=<name>` to store an initial baseline benchmark (e.g. on `main`) and then use `--save-baseline=<name>` to store an initial baseline benchmark (e.g., on `main`) and then use
`--benchmark=<name>` to compare against that benchmark. Criterion will print a message telling you `--benchmark=<name>` to compare against that benchmark. Criterion will print a message telling you
if the benchmark improved/regressed compared to that baseline. if the benchmark improved/regressed compared to that baseline.
@ -678,9 +678,9 @@ utils with it:
23 Newline 24 23 Newline 24
``` ```
- `cargo dev print-cst <file>`: Print the CST of a python file using - `cargo dev print-cst <file>`: Print the CST of a Python file using
[LibCST](https://github.com/Instagram/LibCST), which is used in addition to the RustPython parser [LibCST](https://github.com/Instagram/LibCST), which is used in addition to the RustPython parser
in Ruff. E.g. for `if True: pass # comment` everything including the whitespace is represented: in Ruff. For example, for `if True: pass # comment`, everything, including the whitespace, is represented:
```text ```text
Module { Module {

View file

@ -639,7 +639,7 @@ making changes to code, even for seemingly trivial fixes. If a "safe" fix breaks
Ruff's color output is powered by the [`colored`](https://crates.io/crates/colored) crate, which Ruff's color output is powered by the [`colored`](https://crates.io/crates/colored) crate, which
attempts to automatically detect whether the output stream supports color. However, you can force attempts to automatically detect whether the output stream supports color. However, you can force
colors off by setting the `NO_COLOR` environment variable to any value (e.g., `NO_COLOR=1`), or colors off by setting the `NO_COLOR` environment variable to any value (e.g., `NO_COLOR=1`), or
force colors on by setting `FORCE_COLOR` to any non-empty value (e.g. `FORCE_COLOR=1`). force colors on by setting `FORCE_COLOR` to any non-empty value (e.g., `FORCE_COLOR=1`).
[`colored`](https://crates.io/crates/colored) also supports the `CLICOLOR` and `CLICOLOR_FORCE` [`colored`](https://crates.io/crates/colored) also supports the `CLICOLOR` and `CLICOLOR_FORCE`
environment variables (see the [spec](https://bixense.com/clicolors/)). environment variables (see the [spec](https://bixense.com/clicolors/)).

View file

@ -177,7 +177,7 @@ setting in your configuration file:
``` ```
In our previous example, `--select` with `ALL` `HYP`, `HYP0`, or `HYP00` would not enable `HYP001`. Each preview In our previous example, `--select` with `ALL` `HYP`, `HYP0`, or `HYP00` would not enable `HYP001`. Each preview
rule will need to be selected with its exact code, e.g. `--select ALL,HYP001`. rule will need to be selected with its exact code: for example, `--select ALL,HYP001`.
If preview mode is not enabled, this setting has no effect. If preview mode is not enabled, this setting has no effect.