pub struct CacheMetadata {
pub venv_path: String,
pub requirements_file: Option<String>,
pub requirements_hash: String,
pub manifest_version: Option<String>,
pub manifest_hash: Option<String>,
pub python_version: Option<String>,
}Expand description
Cache metadata persisted next to each venv.
Field names match what client.py’s _save_cache_metadata writes, so
metadata is interchangeable between the two implementations.
manifest_version and manifest_hash are Option to distinguish
“absent” (older metadata, no signal) from “present and different”
(a real change). That distinction is the whole point — see the module
docs.
Fields§
§venv_path: StringAbsolute path of the venv this metadata describes.
requirements_file: Option<String>Absolute path of the requirements file, when there was one.
requirements_hash: StringSHA256 of the requirements file content (empty-content digest when there is no file).
manifest_version: Option<String>Manifest version at install time. Absent in metadata written before this signal existed.
manifest_hash: Option<String>SHA256 of the persisted manifest content. Absent in older metadata.
python_version: Option<String>Interpreter version the venv was built with, for diagnostics.