Struct PypiEcosystem 

pub struct PypiEcosystem { /* private fields */ }

PyPI ecosystem implementation.

Provides LSP functionality for pyproject.toml files, including:

• Dependency parsing with position tracking
• Version information from PyPI registry
• Inlay hints for latest versions
• Hover tooltips with package metadata
• Code actions for version updates
• Diagnostics for unknown/yanked packages

Implementations

impl PypiEcosystem

pub fn new(cache: Arc<HttpCache>) -> PypiEcosystem

Creates a new PyPI ecosystem with the given HTTP cache, using a fresh, default (public_only) deps_core::net_policy::RegistryAccessPolicy private to this ecosystem instance. Production use goes through Self::with_policy instead.

pub fn with_policy( registry: Arc<PypiRegistry>, policy: Arc<RegistryAccessPolicy>, ) -> PypiEcosystem

Creates a new PyPI ecosystem around an existing PypiRegistry instance, sharing policy’s live reachability setting — the production constructor, used by deps-lsp’s register_ecosystems so initialize/workspace/didChangeConfiguration updating the same Arc<RegistryAccessPolicy> takes effect immediately, with no need to reconstruct the ecosystem.

Trait Implementations

impl Ecosystem for PypiEcosystem

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

Unique identifier (e.g., “cargo”, “npm”, “pypi”)

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

Human-readable name (e.g., “Cargo (Rust)”, “npm (JavaScript)”)

fn manifest_filenames(&self) -> &[&'static str]

Manifest filenames this ecosystem handles (e.g., [“Cargo.toml”])

fn manifest_patterns(&self) -> &[&'static str]

Basename glob patterns this ecosystem handles, each containing exactly one * wildcard (e.g. ["requirements*.txt"]).

fn manifest_directory_patterns(&self) -> &[(&'static str, &'static str)]

(directory_path, file_suffix) pairs identifying a file solely by its containing directory path and suffix. directory_path may be a single segment (e.g. [("requirements", ".txt")] for Python’s requirements/base.txt split-file layout) or multiple /-joined segments (e.g. [(".github/workflows", ".yml")] for GitHub Actions workflow files) — either way it is matched against the tail of the file’s directory path on segment boundaries, not just the immediate parent, so a multi-segment pattern matches regardless of how many ancestor directories precede it. Used when the basename alone carries no ecosystem signal.

fn lockfile_filenames(&self) -> &[&'static str]

Lock file filenames this ecosystem uses (e.g., [“Cargo.lock”])

fn parse_manifest<'a>( &'a self, content: &'a str, uri: &'a Uri, ) -> Pin<Box<dyn Future<Output = Result<Box<dyn ParseResult>, DepsError>> + Send + 'a>>

Parse a manifest file and return parsed result

fn registry(&self) -> Arc<dyn Registry>

Get the registry client for this ecosystem

fn lockfile_provider(&self) -> Option<Arc<dyn LockFileProvider>>

Get the lock file provider for this ecosystem.

fn formatter(&self) -> &dyn EcosystemFormatter

Get the ecosystem-specific formatter for LSP response generation.

fn generate_completions<'a>( &'a self, parse_result: &'a dyn ParseResult, position: Position, content: &'a str, freshness: FreshnessSettings, ) -> Pin<Box<dyn Future<Output = Completions> + Send + 'a>>

Generate completions for a position.

fn package_search_is_incomplete(&self) -> bool

Whether this ecosystem’s package-name search may return a truncated view of a larger candidate set (see e.g. PypiRegistry::search’s doc comment).

fn generate_document_links( &self, parse_result: &dyn ParseResult, uri: &Uri, ) -> Vec<DocumentLink>

Generate textDocument/documentLink targets for the document.

fn as_any(&self) -> &(dyn Any + 'static)

Support for downcasting to concrete ecosystem type

fn manifest_extensions(&self) -> &[&'static str]

File extensions this ecosystem handles when the manifest basename is not fixed (e.g. [".csproj", ".fsproj"] for NuGet project files).

fn watched_config_filenames(&self) -> &[&'static str]

Non-lockfile config filenames this ecosystem resolves during Self::parse_manifest (e.g. ["pnpm-workspace.yaml", ".npmrc"] for npm’s catalog and registry resolution), whose values end up baked into a manifest’s ParseResult rather than looked up separately the way a Self::lockfile_provider is.

fn generate_inlay_hints<'a>( &'a self, parse_result: &'a dyn ParseResult, versions: VersionData<'a>, loading_state: LoadingState, config: &'a EcosystemConfig, ) -> Pin<Box<dyn Future<Output = Vec<InlayHint>> + Send + 'a>>

Generate inlay hints for the document.

fn generate_hover<'a>( &'a self, parse_result: &'a dyn ParseResult, position: Position, versions: VersionData<'a>, freshness: FreshnessSettings, ) -> Pin<Box<dyn Future<Output = Option<Hover>> + Send + 'a>>

Generate hover information for a position.

fn generate_code_actions<'a>( &'a self, parse_result: &'a dyn ParseResult, position: Position, uri: &'a Uri, versions: VersionData<'a>, content: &'a str, ) -> Pin<Box<dyn Future<Output = Vec<CodeAction>> + Send + 'a>>

Generate code actions for a position.

fn generate_diagnostics<'a>( &'a self, parse_result: &'a dyn ParseResult, versions: VersionData<'a>, uri: &'a Uri, freshness: FreshnessSettings, severities: DiagnosticSeverities, ) -> Pin<Box<dyn Future<Output = Vec<Diagnostic>> + Send + 'a>>

Generate diagnostics for the document.

fn generate_code_lenses<'a>( &'a self, parse_result: &'a dyn ParseResult, content: &'a str, versions: VersionData<'a>, uri: &'a Uri, command_id: &'a str, ) -> Pin<Box<dyn Future<Output = Vec<CodeLens>> + Send + 'a>>

Generate the “Update N outdated dependencies” code lens for the document.

impl Sealed for PypiEcosystem