Struct PypiFormatter 

pub struct PypiFormatter;

Trait Implementations

impl DiagnosticMessages for PypiFormatter

fn yanked_message(&self) -> &'static str

Message for yanked/deprecated versions in diagnostics.

fn yanked_label(&self) -> &'static str

Label for yanked versions in hover.

fn deprecated_message(&self) -> &'static str

Message for a package-level deprecation/abandonment diagnostic (issue #205).

fn deprecated_label(&self) -> &'static str

Label for a deprecated package in hover.

impl DiagnosticPolicy for PypiFormatter

fn strict_semver_prerelease_exclusion(&self) -> bool

Whether this ecosystem’s requirement/version syntax follows strict SemVer 2.0.0 pre-release semantics: a pre-release version (X.Y.Z-pre) is excluded from matching requirement unless requirement itself pins to the same X.Y.Z tuple with a pre-release tag — the rule Cargo’s semver crate and npm’s node-semver both implement, and that compile_requirement’s matcher inherits from its underlying comparator.

fn supports_package_rename(&self) -> bool

Whether this ecosystem’s deprecation payload (crate::Deprecation::replacement) is safe to offer as a “Replace with X” rename quickfix.

fn yanked_diagnostic_applies_to( &self, _dep: &dyn Dependency, _requirement: &VersionReq, ) -> bool

Whether the “requirement satisfiable only by a yanked version” diagnostic (crate::lsp_helpers::requirement_matches_only_yanked) should evaluate requirement at all for this ecosystem.

impl OsvNaming for PypiFormatter

fn osv_package_name(&self, dep: &dyn Dependency) -> Option<String>

OSV.dev’s canonical spelling for dep’s package name, or None if this dependency cannot be mapped (e.g. a non-GitHub Swift package).

fn osv_version_to_native(&self, version: &str) -> String

Converts a version string as it appears in an OSV advisory record (e.g. crate::osv::Advisory::fixed_versions) into this ecosystem’s own version namespace, as used in manifests and by the registry.

fn osv_version(&self, version: &str) -> String

Rewrites a native-ecosystem version string into the spelling OSV.dev’s SEMVER range matching expects.

impl PackageNaming for PypiFormatter

fn normalize_package_name(&self, name: &PackageName) -> String

Normalize package name for lookup (default: identity).

fn validate_package_name(&self, name: &str) -> Result<(), InvalidPackageName>

Lints name against ecosystem-specific naming rules.

impl PackageRendering for PypiFormatter

fn suppress_package_url(&self, source: &DependencySource) -> bool

FR-009/validator finding #2: suppresses the hover heading’s pypi.org project link for anything but plain public-registry content. Without this override (the trait default is unconditionally false), a private-index dependency’s hover would render a pypi.org link right next to its actual private-index version data — once live data renders alongside it, an unrelated pypi.org link reads as false confirmation the link is real. Mirrors NpmFormatter’s/CargoFormatter’s identical override, reusing SourcePolicy::source_is_public_registry_content’s default (Registry only — PyPI has no crates.io-style verified-mirror concept for AlternateRegistry to except).

fn format_version_for_text_edit(&self, version: &ConcreteVersion) -> String

Format version string for code action text edit.

fn format_version_replacing( &self, version: &ConcreteVersion, current: &str, ) -> String

Format version as a replacement for the existing requirement text current, preserving current’s operator/pin style where the ecosystem supports more than one.

fn package_url(&self, name: &PackageName) -> String

Get package URL for hover markdown.

fn is_position_on_dependency( &self, dep: &dyn Dependency, position: Position, ) -> bool

Detect if cursor position is on a dependency for code actions.

fn format_version_replacing_for( &self, _dep: &dyn Dependency, version: &ConcreteVersion, current: &str, ) -> String

Like format_version_replacing, but also carries the dependency identity version/current apply to.

impl RequirementResolution for PypiFormatter

fn compile_requirement( &self, requirement: &VersionReq, ) -> Option<Box<dyn RequirementMatcher>>

Compiles requirement via pep440_rs::VersionSpecifiers — the same crate and the same precise contains-check version_satisfies_requirement above already uses, so this is not a new comparator, just its result cached across candidates instead of reparsed per call.

Returns None when any specifier pins a PEP 440 local version identifier (e.g. torch==2.0.1+cu118). Local versions are conventionally published only on custom/alternate indexes (e.g. the PyTorch wheel index), not the default registry this matcher checks candidates against — so an empty match set there does not mean the requirement is unsatisfiable everywhere, and the diagnostic would be a false positive.

fn version_satisfies_requirement( &self, version: &ConcreteVersion, requirement: &str, ) -> bool

Check if a version satisfies a requirement string.

fn is_requirement_up_to_date( &self, requirement: &VersionReq, latest: &ConcreteVersion, ) -> bool

Whether an unresolved dependency (no lock-file version) should be reported as up to date against latest, given its declared requirement.

fn requirement_is_unresolved(&self, _requirement: &VersionReq) -> bool

Whether requirement could not be resolved to a concrete version constraint (e.g. an unexpanded property/variable placeholder rather than a real version or range).

fn requirement_status( &self, requirement: &VersionReq, latest: &ConcreteVersion, ) -> RequirementStatus

Tri-state variant of is_requirement_up_to_date that distinguishes “confirmed up to date” from “could not be resolved, so we don’t know.”

fn requirement_status_for( &self, dep: &dyn Dependency, requirement: &VersionReq, latest: &ConcreteVersion, ) -> RequirementStatus

Like requirement_status, but also hands the ecosystem the dependency itself — for an ecosystem whose requirement text alone is ambiguous between two shapes with different resolution rules, and which already computed the disambiguating classification once, at parse time, onto the dependency (deps-gitlab-ci’s PinStyle, #466 review M-c: a bare "1.2" is Partial under its component: pin grammar but Branch under its simpler project: ref grammar — indistinguishable from the text alone).

fn requirement_is_undecidable_given_available( &self, _requirement: &VersionReq, _available: &[ConcreteVersion], ) -> bool

Whether this ecosystem’s registry can silently omit a published version from available in a way indistinguishable from “never published” — and, if so, whether requirement names a version-space region that specific omission could explain, given the versions actually observed in available.

fn manifest_requirement_is_resolved_version(&self, dep: &dyn Dependency) -> bool

Whether dep’s manifest version-requirement line is itself the exact version already selected — never a range.

impl SourcePolicy for PypiFormatter

fn can_resolve_source(&self, source: &DependencySource) -> bool

FR-009: gates hover/diagnostics/code-actions on a resolved AlternateRegistry (private-index) source, in addition to the plain public Registry default — mirrors NpmFormatter::can_resolve_source exactly. CustomRegistry (an unresolved or invalid explicit index — FR-006) is deliberately not accepted here: it falls through to the default is_version_resolvable() == false, keeping the existing fail-closed gate intact.

Known cosmetic limitation (M1, not fixed): a plain dependency in an extras-only file (FR-005(b)) is classified AlternateRegistry at parse time, before the winning hop is known — if it actually resolves via the implicit public fallback, its pypi.org hover link is still suppressed by PackageRendering::suppress_package_url (correct for the private-index case this feature exists for, cosmetically over-cautious only for this one edge case). Accepted for phase 1; documented in ECOSYSTEM_GUIDE.md.

fn source_is_public_registry_content(&self, source: &DependencySource) -> bool

Whether source’s content is exactly the default public registry’s — safe to treat as such for OSV vulnerability scanning, cache-key signature construction, and hover heading links.