astral-sh/uv · error
Project is already initialized in `{}` (`pyproject.toml` fil
Error message
Project is already initialized in `{}` (`pyproject.toml` file exists) What it means
Error "Project is already initialized in `{}` (`pyproject.toml` file exists)" thrown in astral-sh/uv.
Source
Thrown at crates/uv/src/commands/project/init.rs:108
writeln!(
printer.stderr(),
"Initialized script at `{}`",
path.user_display().cyan()
)?;
}
InitKind::Project(project_kind) => {
// Default to the current directory if a path was not provided.
let path = match explicit_path {
None => project_dir.to_path_buf(),
Some(ref path) => std::path::absolute(path)?,
};
// Make sure a project does not already exist in the given directory.
if path.join("pyproject.toml").exists() {
let path =
std::path::absolute(&path).unwrap_or_else(|_| path.simplified().to_path_buf());
anyhow::bail!(
"Project is already initialized in `{}` (`pyproject.toml` file exists)",
path.display().cyan()
);
}
// Default to the directory name if a name was not provided.
let name = match name {
Some(name) => name,
None => {
let directory_name = path
.file_name()
.and_then(|path| path.to_str())
.context("Missing directory name")?;
// Pre-normalize the package name by removing any leading or trailing
// whitespace, and replacing any internal whitespace with hyphens.
let candidate = directory_name.trim().replace(' ', "-");
match PackageName::from_owned(candidate) {View on GitHub (pinned to f1a42680ff)
When it happens
Trigger: Thrown at crates/uv/src/commands/project/init.rs:108 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of astral-sh/uv@f1a42680ff (2026-08-16).
Data as JSON: /api/errors/8c6b5487b541992e.
Report an issue: GitHub.