mirrors/ruff
1
0
Fork 0
mirror of https://github.com/astral-sh/ruff.git synced 2025-10-01 14:21:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

[red-knot] Remove mentions of Ruff from the CLI help (#12752)

Browse source 
Co-authored-by: Micha Reiser <micha@reiser.io>
This commit is contained in:
Alex Waygood 2024-08-08 15:35:10 +01:00 • committed by GitHub
parent f1de08c2a0
commit d28c5afd14
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 18 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

23
crates/red_knot/src/main.rs
View file

@ -27,7 +27,7 @@ mod verbosity;
#[command( #[command(
author, author,
name = "red-knot", name = "red-knot",
about = "An experimental multifile analysis backend for Ruff" about = "An extremely fast Python type checker."
)] )]
#[command(version)] #[command(version)]
struct Args { struct Args {
@ -67,7 +67,12 @@ to resolve type information for the project's third-party dependencies.",
)] )]
extra_search_path: Vec<SystemPathBuf>, extra_search_path: Vec<SystemPathBuf>,
#[arg(long, help = "Python version to assume when resolving types", default_value_t = TargetVersion::default(), value_name="VERSION")] #[arg(
long,
help = "Python version to assume when resolving types",
default_value_t = TargetVersion::default(),
value_name="VERSION")
]
target_version: TargetVersion, target_version: TargetVersion,
#[clap(flatten)] #[clap(flatten)]
@ -97,7 +102,7 @@ pub fn main() -> ExitStatus {
// This communicates that this isn't a linter error but Red Knot itself hard-errored for // This communicates that this isn't a linter error but Red Knot itself hard-errored for
// some reason (e.g. failed to resolve the configuration) // some reason (e.g. failed to resolve the configuration)
writeln!(stderr, "{}", "ruff failed".red().bold()).ok(); writeln!(stderr, "{}", "Red Knot failed".red().bold()).ok();
// Currently we generally only see one error, but e.g. with io errors when resolving // Currently we generally only see one error, but e.g. with io errors when resolving
// the configuration it is help to chain errors ("resolving configuration failed" -> // the configuration it is help to chain errors ("resolving configuration failed" ->
// "failed to read file: subdir/pyproject.toml") // "failed to read file: subdir/pyproject.toml")
@ -132,7 +137,13 @@ fn run() -> anyhow::Result<ExitStatus> {
// The base path to which all CLI arguments are relative to. // The base path to which all CLI arguments are relative to.
let cli_base_path = { let cli_base_path = {
let cwd = std::env::current_dir().context("Failed to get the current working directory")?; let cwd = std::env::current_dir().context("Failed to get the current working directory")?;
SystemPathBuf::from_path_buf(cwd).map_err(|path| anyhow!("The current working directory '{}' contains non-unicode characters. Red Knot only supports unicode paths.", path.display()))? SystemPathBuf::from_path_buf(cwd)
.map_err(|path| {
anyhow!(
"The current working directory '{}' contains non-unicode characters. Red Knot only supports unicode paths.",
path.display()
)
})?
}; };
let cwd = current_directory let cwd = current_directory
@ -308,7 +319,9 @@ impl MainLoop {
tracing::error!("{}", diagnostic); tracing::error!("{}", diagnostic);
} }
} else { } else {
tracing::debug!("Discarding check result for outdated revision: current: {revision}, result revision: {check_revision}"); tracing::debug!(
"Discarding check result for outdated revision: current: {revision}, result revision: {check_revision}"
);
} }
if self.watcher.is_none() { if self.watcher.is_none() {