Enum PypiError 

#[non_exhaustive]
pub enum PypiError {
    TomlParseError {
        message: String,
    },
    InvalidDependencySpec {
        source: Pep508Error,
    },
    UnsupportedFormat {
        message: String,
    },
    RequirementTooLong {
        len: usize,
        max: usize,
    },
}

Errors specific to PyPI/Python dependency handling.

These errors cover parsing pyproject.toml files and validating PEP 508 dependency specifications. Registry communication errors are reported as deps_core::DepsError directly (see crate::registry).

#[non_exhaustive] (matching crate::types::PypiDependencySection): this enum grows as new parse-failure modes are distinguished (e.g. PypiError::RequirementTooLong, added without a matching cargo-semver-checks gate), so an external exhaustive match must not be able to break on a future addition.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

TomlParseError

Failed to parse pyproject.toml

Fields

message: String

InvalidDependencySpec

Invalid PEP 508 dependency specification

Fields

source: Pep508Error

UnsupportedFormat

Unsupported dependency format

Fields

message: String

RequirementTooLong

PEP 508 requirement string exceeded the length cap protecting against pep508_rs’s O(n²) extras-list parser (see crate::parser::MAX_REQUIREMENT_LEN). Kept as a distinct variant (rather than folded into UnsupportedFormat) so callers can tell a deliberate length rejection apart from a genuine syntax error — the two must be counted differently by heuristics like the requirements.txt “is this really a manifest” signal.

Fields

len: usize

max: usize

Implementations

impl PypiError

pub fn unsupported_format(message: impl Into<String>) -> Self

Create an unsupported format error.

Trait Implementations

impl Debug for PypiError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for PypiError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for PypiError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.