`ptwm_core::install::pip`

Pip-package install source. Two paths:

rsmod

ptwm_core::install::pip

mod pip

Pip-package install source. Two paths:

1. If `python -c "import <name>"` already succeeds (or `importlib.metadata.distribution(name)` succeeds), no-op. 2. Otherwise invoke `python -m pip install <name>` in a subprocess. For both paths, the actual contribution registration happens later at PTWM startup via `python/ptwm/_loader.py::load_all_host_extensions`. The Rust-side `install` doesn't return a bundle directory — pip installs into the site-packages, not into the user extensions dir.

rsfn

ptwm_core::install::pip::install_pip_package

crates/ptwm-core/src/install/pip.rs:22

pub fn install_pip_package(name: &str) -> Result<PipInstallOutcome, ExtensionError>

rsfn

ptwm_core::install::pip::install_pip_package_with

crates/ptwm-core/src/install/pip.rs:26

pub fn install_pip_package_with(python: &str, name: &str) -> Result<PipInstallOutcome, ExtensionError>

rstype

ptwm_core::install::pip::PipInstallOutcome

crates/ptwm-core/src/install/pip.rs:17

pub enum PipInstallOutcome