SandboxRegistry(
self,
*,
config: SandboxConfig | None = None,
include_entry_points: bool = | Name | Type | Description |
|---|---|---|
config | SandboxConfig | None | Default: None |
include_entry_points | bool | Default: True |
| Name | Type |
|---|---|
| config | SandboxConfig | None |
| include_entry_points | bool |
Merged view of built-in, entry-point, and config sandbox providers.
Parsed sandbox config. Loaded from the default path when omitted.
Whether to discover entry-point providers. Disabled in tests that need a deterministic provider set.
The configured default provider, if any.
Why the config file failed to load, if it existed but couldn't parse.
None when the config parsed cleanly or simply wasn't present.
Build a registry from the config file at config_path.
Return all known provider names, sorted.
Return whether name resolves to a known provider.
Return metadata for name.
Config providers may override working_dir, package, and capability
flags. Entry-point providers are probed for advertised metadata and
take precedence over built-ins with the same name.
Return config params forwarded to the provider's get_or_create().
Instantiate the provider named name.
Resolution order: config class_path > entry point > built-in.
Return authoritative metadata for name.
Config providers are described statically. Entry-point providers are
instantiated so capability flags they expose via a metadata attribute
take effect; on failure this falls back to the static placeholder.
Built-in metadata is used only when no entry point overrides that name.