Failed to parse dependency from {table_name} in `{}`: {messa

Error message

Failed to parse dependency from {table_name} in `{}`: {message}

What it means

Error "Failed to parse dependency from {table_name} in `{}`: {message}" thrown in astral-sh/uv.

Source

Thrown at crates/uv/src/commands/project/upgrade.rs:594

        }
        return Ok(true);
    }

    Ok(false)
}

fn parse_dependency(
    dependency: &str,
    table_name: &str,
    pyproject_path: &Path,
) -> Result<Requirement<VerbatimParsedUrl>> {
    Requirement::<VerbatimParsedUrl>::from_str(dependency).map_err(|error| {
        let message = match error.message {
            Pep508ErrorSource::String(message)
            | Pep508ErrorSource::UnsupportedRequirement(message) => message,
            Pep508ErrorSource::UrlError(_) => "Invalid URL requirement".to_string(),
        };
        anyhow!(
            "Failed to parse dependency from {table_name} in `{}`: {message}",
            pyproject_path.display()
        )
    })
}

/// Select the dependency declarations targeted by `uv upgrade`.
fn select_requirements(
    project: &ProjectWorkspace,
    packages: &[PackageName],
    exclude: &[PackageName],
    fallback_interpreter: Option<&Interpreter>,
) -> Result<DeclarationSelection> {
    if project.workspace().packages().len() != 1 {
        bail!("`uv upgrade` does not support workspaces with multiple members yet");
    }

    let is_explicit_selection = !packages.is_empty();

View on GitHub (pinned to f1a42680ff)

When it happens

Trigger: Thrown at crates/uv/src/commands/project/upgrade.rs:594 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

Parsing and encoding errors: unexpected token, malformed input — why parsers reject input and how to find the real culprit.

AI-assisted analysis of astral-sh/uv@f1a42680ff (2026-08-16). Data as JSON: /api/errors/a3585ab56ec7a225. Report an issue: GitHub.