scikit_build_core.settings package¶
Submodules¶
scikit_build_core.settings.auto_cmake_version module¶
scikit_build_core.settings.auto_requires module¶
scikit_build_core.settings.documentation module¶
scikit_build_core.settings.json_schema module¶
scikit_build_core.settings.skbuild_docs_readme module¶
scikit_build_core.settings.skbuild_docs_sphinx module¶
Make documentation for the skbuild model in sphinx format.
scikit_build_core.settings.skbuild_model module¶
- class scikit_build_core.settings.skbuild_model.BackportSettings(find_python=<Version('3.26.1')>)[source]¶
Bases:
object
- class scikit_build_core.settings.skbuild_model.BuildSettings(tool_args=<factory>, targets=<factory>, verbose=False, requires=<factory>)[source]¶
Bases:
object- requires: List[str]¶
Additional
build-system.requires.Intended to be used in combination with
overrides.
- class scikit_build_core.settings.skbuild_model.CMakeSettings(minimum_version=None, version=None, args=<factory>, define=<factory>, verbose=None, build_type='Release', source_dir=PosixPath('.'), targets=None, toolchain_file=None, python_hints=True)[source]¶
Bases:
object- args: List[str]¶
A list of args to pass to CMake when configuring the project.
Setting this in config or envvar will override toml.
See also
- build_type: str | List[str] = 'Release'¶
The build type to use when building the project.
Pre-defined CMake options are:
Debug,Release,RelWithDebInfo,MinSizeRelCustom values can also be used.
A list of build types can be given to build and install more than one configuration into the same wheel:
["Release", "Debug"]in TOML, a repeated-Ccmake.build-type=...config-setting, orRelease;Debugas an environment variable. Single-config generators (Ninja, Makefiles) are reconfigured in place for each extra build type; multi-config generators (Visual Studio, Xcode, Ninja Multi-Config) build each--config. Every build type is installed to the same prefix, so useCMAKE_<CONFIG>_POSTFIXto avoid clobbering files between configurations.Changed in version 1.0: A list of build types can now be given.
- define: Annotated[Dict[str, CMakeSettingsDefine], 'EnvVar']¶
A table of defines to pass to CMake when configuring the project. Additive.
- python_hints: bool = True¶
Do not pass the current environment’s python hints such as
Python_EXECUTABLE. Primarily used for cross-compilation where the CMAKE_TOOLCHAIN_FILE should handle it instead.
- source_dir: Path = PosixPath('.')¶
The source directory to use when building the project.
Currently only affects the native builder (not the setuptools plugin).
- toolchain_file: Path | None = None¶
The CMAKE_TOOLCHAIN_FILE / –toolchain used for cross-compilation.
This cannot be set in the static
[tool.scikit-build]table; use it in an override, config-settings, or an environment variable.
- version: SpecifierSet | None = None¶
The versions of CMake to allow as a python-compatible specifier.
If CMake is not present on the system or does not pass this specifier, it will be downloaded via PyPI if possible with the equivalent specifier used.
An empty string will disable this check.
- Special cases:
On scikit-build-core 0.10+
CMakeLists.txtis the default value otherwise it’s>=3.15.If
CMakeLists.txtis passed, thecmake_minimum_requiredis read from the CMakeLists.txt file, using that as the minimum specifier. If the file fails to read,>=3.15is used instead.
See also
- class scikit_build_core.settings.skbuild_model.CMakeSettingsDefine(raw: str | bool | List[str])[source]¶
Bases:
strA str subtype for automatically normalizing bool and list values to the CMake representation in the cmake.define settings key.
- json_schema = str | bool | typing.List[str]¶
- class scikit_build_core.settings.skbuild_model.EditableSettings(mode='redirect', verbose=True, rebuild=False, rebuild_dir='')[source]¶
Bases:
object- mode: Literal['redirect', 'inplace'] = 'redirect'¶
Select the editable mode to use. Can be “redirect” (default) or “inplace”.
- rebuild: bool = False¶
Rebuild the project when the package is imported.
build-dirmust be set, except ininplacemode (where the source directory is the build directory).
- rebuild_dir: str = ''¶
Install rebuildable editables into this tree (a newer alternative to
editable.rebuild).Setting this turns on rebuild-on-import by itself; the
editable.rebuildflag is ignored when it is set. The compiled artifacts are installed here at first build and re-installed in place on every import-triggered rebuild, and the redirect references them by absolute path. Must be an absolute (or source-relative) path that is stable between build and run time, and supports the same template substitutions asbuild-dir. This relocates only the install tree;build-diris still required and still hosts the CMake build that the rebuild re-runs.The tree is wiped and recreated on each build, so it must be a fresh or scikit-build-core-managed directory – pointing it at a populated directory such as your source tree is refused to avoid deleting those files. A managed tree gets a
CACHEDIR.TAGand a.gitignoreso its compiled artifacts stay out of backups and version control.Added in version 1.0.
- class scikit_build_core.settings.skbuild_model.EnvValue(raw)[source]¶
Bases:
objectA single entry in the top-level
envtable.Accepts either a literal string or a table with
env/default/forcekeys. Resolution against the build environment is deferred toresolve()so that theforceflag survives parsing (unlike thecmake.defineEnvVarform, which resolves at parse time). A bare string is shorthand for{ default = "<string>" }.
- class scikit_build_core.settings.skbuild_model.GenerateSettings(path, template='', template_path=None, location='install')[source]¶
Bases:
object- location: Literal['install', 'build', 'source'] = 'install'¶
The place to put the generated file.
The
builddirectory is useful for CMake files, and theinstalldirectory is useful for Python files, usually. You can also write directly to thesourcedirectory, will overwrite existing files & remember to gitignore the file.
- template: str = ''¶
The template string to use for the file.
Template style placeholders are available for all the metadata.
Either this or
generate[].template-pathmust be set.See also
- template_path: Path | None = None¶
The path to the template file. If empty, a template must be set.
Either this or
generate[].templatemust be set.See also
- class scikit_build_core.settings.skbuild_model.InstallSettings(components=<factory>, targets=<factory>, strip=None)[source]¶
Bases:
object- components: List[str]¶
The components to install.
If not specified or an empty list, all default components are installed.
- strip: bool | None = None¶
Whether to strip the binaries.
Equivalent to
--stripincmake install.True for release builds (Release or MinSizeRel) on scikit-build-core 0.5+.
Note
0.5-0.10.5 also incorrectly set this for debug builds.
- targets: List[str]¶
Build targets to run during the install step via
cmake --build --target.This is intended for projects that group their install rules under an umbrella “distribution” build target (such as LLVM’s
install-distribution) rather than using CMake installCOMPONENTs. Each listed target is built, which triggers its install rules into the staging prefix.This relies on the configure-time
CMAKE_INSTALL_PREFIX(set automatically by scikit-build-core to the wheel staging directory); the--stripand--componentoptions ofcmake --installdo not apply to these targets.componentsandtargetsmay be combined; both will run.Added in version 1.0.
- class scikit_build_core.settings.skbuild_model.LoggingSettings(level='WARNING')[source]¶
Bases:
object
- class scikit_build_core.settings.skbuild_model.MessagesSettings(after_failure='', after_success='')[source]¶
Bases:
objectSettings for messages.
- class scikit_build_core.settings.skbuild_model.NinjaSettings(minimum_version=None, version=<SpecifierSet('>=1.5')>, make_fallback=True)[source]¶
Bases:
object- make_fallback: bool = True¶
Use Make as a fallback if a suitable Ninja executable is not found.
If Make is also not available on the system, a ninja dependency is added to the
build-system.requiresaccording toninja.version.See also
- version: SpecifierSet = <SpecifierSet('>=1.5')>¶
The versions of Ninja to allow.
If Ninja is not present on the system or does not pass this specifier, it will be downloaded via PyPI if possible with the equivalent specifier used.
An empty string will disable this check.
See also
- class scikit_build_core.settings.skbuild_model.SDistSettings(include=<factory>, exclude=<factory>, inclusion_mode=None, reproducible=True, cmake=False, force_include=<factory>, resolve_symlinks=None)[source]¶
Bases:
object- exclude: List[str]¶
Files to exclude from the SDist even if they are included by default. Supports gitignore syntax.
See also
- force_include: Dict[str, str]¶
Force-include files into the SDist.
Maps source paths to destinations relative to the SDist root. Keys are relative to the project root; they may point outside it (e.g.
../shared) or be absolute, and~is expanded. A source may be a file or a directory; directories are copied recursively, skipping VCS and__pycache__junk.Force-included files override files at the same destination. A missing source is an error.
A force-included file is forced in even if
sdist.excludematches its destination, since naming an exact source is an explicit request. A force-included directory stays subject tosdist.exclude, so a bulk copy can still be trimmed by an exclude pattern.Added in version 1.0.
- include: List[str]¶
Files to include in the SDist even if they are skipped by default. Supports gitignore syntax.
Always takes precedence over
sdist.excludeSee also
- inclusion_mode: Literal['classic', 'default', 'manual', 'explicit'] | None = None¶
Method to use to compute the files to include and exclude.
The methods are:
“default”: Process the git ignore files. Shortcuts on ignored directories.
“classic”: The behavior before 0.12, like “default” but does not shortcut directories.
“manual”: No extra logic, based on include/exclude only.
“explicit”: Opt-in only. Nothing is included unless it matches an
includepattern, andexcludeis applied after, so it can trim included files back out. Like “manual”, git ignore files are not read.
If you don’t set this, it will be “default” unless you set the minimum version below 0.12, in which case it will be “classic”.
Added in version 0.12.
Changed in version 1.0: Added the “explicit” mode.
- reproducible: bool = True¶
Try to build a reproducible distribution.
Unix and Python 3.9+ recommended.
SOURCE_DATE_EPOCHwill be used for timestamps, or a fixed value if not set.
- resolve_symlinks: Literal['all', 'external', 'none', 'classic'] | None = None¶
Which symlinks to resolve in the SDist, storing the target’s contents instead.
The modes are:
“all”: Resolve every symlink, copying its target’s contents.
“external”: Resolve only symlinks that point outside the project (those would be broken once the SDist is extracted); store symlinks that stay inside the project as-is.
“none”: Store every symlink as-is, including directory symlinks.
“classic”: Store file symlinks as-is, but follow directory symlinks, copying their contents (scikit-build-core 0.x behavior).
A symlink that can’t be resolved (dangling, or a directory symlink loop) is stored as a symlink in every mode, with a warning if it was supposed to be resolved.
If you don’t set this, it will be “all” unless you set the minimum version below 1.0, in which case it will be “classic” to preserve backward compatibility.
Added in version 1.0.
- class scikit_build_core.settings.skbuild_model.ScikitBuildSettings(cmake=<factory>, ninja=<factory>, logging=<factory>, sdist=<factory>, wheel=<factory>, backport=<factory>, editable=<factory>, build=<factory>, install=<factory>, generate=<factory>, messages=<factory>, search=<factory>, metadata=<factory>, env=<factory>, strict_config=True, experimental=False, variant=<factory>, variant_name=<factory>, variant_label=None, null_variant=False, minimum_version=None, build_dir='', fail=None)[source]¶
Bases:
object- backport: BackportSettings¶
- build: BuildSettings¶
- build_dir: str = ''¶
The CMake build directory. Defaults to a unique temporary directory.
This can be set to reuse the build directory from previous runs.
- cmake: CMakeSettings¶
- editable: EditableSettings¶
- env: Annotated[Dict[str, EnvValue], 'EnvTable']¶
A table of environment variables to set for the CMake subprocesses.
Applied to the configure, build, and install steps. A variable is only set if not already present (like a
setdefault); passforce = trueto overwrite. Each value is a literal string or a table withenv(read from another environment variable),default, andforce; an entry that resolves to nothing is skipped. Independent of theif.envoverride condition.Added in version 1.0.
- fail: bool | None = None¶
Immediately fail the build. This cannot be set in the static
[tool.scikit-build]table; use it in an override, config-settings, or an environment variable.
- generate: List[GenerateSettings]¶
- install: InstallSettings¶
- logging: LoggingSettings¶
- messages: MessagesSettings¶
- minimum_version: Version | None = None¶
If set, this will provide a method for backward compatibility.
- ninja: NinjaSettings¶
- null_variant: bool = False¶
Experimental PEP 817 null-variant selector.
This cannot be set in the static
[tool.scikit-build]table; use it in an override, config-settings, or an environment variable.Added in version 1.0.
- sdist: SDistSettings¶
- search: SearchSettings¶
- strict_config: bool = True¶
Strictly check all config options.
If False, warnings will be printed for unknown options.
If True, an error will be raised.
- variant: List[str]¶
Experimental PEP 817 variant properties.
This cannot be set in the static
[tool.scikit-build]table; use it in an override, config-settings, or an environment variable.Added in version 1.0.
- variant_label: str | None = None¶
Experimental PEP 817 wheel variant label override.
This cannot be set in the static
[tool.scikit-build]table; use it in an override, config-settings, or an environment variable.Added in version 1.0.
- variant_name: List[str]¶
Experimental PEP 817 variant properties used for wheel metadata selection.
This cannot be set in the static
[tool.scikit-build]table; use it in an override, config-settings, or an environment variable.Added in version 1.0.
- wheel: WheelSettings¶
- class scikit_build_core.settings.skbuild_model.SearchSettings(site_packages=True)[source]¶
Bases:
object
- class scikit_build_core.settings.skbuild_model.WheelSettings(packages=None, py_api='', expand_macos_universal_tags=False, install_dir='', license_files=None, cmake=True, platlib=None, exclude=<factory>, build_tag='', tags=None, force_include=<factory>, reproducible=False)[source]¶
Bases:
object- exclude: List[str]¶
A set of patterns to exclude from the wheel.
This is additive to the SDist exclude patterns. This applies to the final paths in the wheel, and can exclude files from CMake output as well. Editable installs may not respect this exclusion.
- expand_macos_universal_tags: bool = False¶
Fill out extra tags that are not required.
This adds “x86_64” and “arm64” to the list of platforms when “universal2” is used, which helps older Pip’s (before 21.0.1) find the correct wheel.
- force_include: Dict[str, str]¶
Force-include files into the wheel.
Maps source paths to destinations relative to the platlib (the package area). Keys are relative to the project root; they may point outside it (e.g.
../shared) or be absolute, and~is expanded. A source may be a file or a directory; directories are copied recursively, skipping VCS and__pycache__junk.A
${SKBUILD_<TREE>_DIR}prefix (e.g.${SKBUILD_DATA_DIR}/foo) targets that wheel tree instead of the platlib, matching theSKBUILD_*_DIRCMake cache variables (DATA,SCRIPTS,HEADERS,PLATLIB,METADATA, …). The deprecated leading-slash form (/data,/scripts, …) selects the same trees but requiresexperimental.Force-included files are placed last, so they override discovered package files and CMake output at the same destination. A missing source is an error.
A force-included file also overrides
wheel.exclude, since naming an exact source is an explicit request for that file. A force-included directory stays subject towheel.exclude, so a bulk copy can still be trimmed by an exclude pattern.If a source is missing on disk, it is looked up through
sdist.force-include(by exact destination or under a force-included directory) and read from that original source instead. This lets a source that names an sdist output (vendored viasdist.force-include) build from both a source tree and an unpacked sdist.In a redirect-mode editable install, platlib entries are served live from their sources through the import redirect instead of being copied: importable modules always, data files when they keep their filename and sit directly inside a top-level package. Anything else (other wheel trees; renamed, top-level, or nested data files) is still copied at install time.
Added in version 1.0.
- install_dir: str = ''¶
The CMake install prefix relative to the platlib wheel path.
You might set this to the package name to install everything under the package namespace in a pythonic design.
The original dir is still at
SKBUILD_PLATLIB_DIR(alsoSKBUILD_DATA_DIR, etc. are available).A
${SKBUILD_<TREE>_DIR}prefix (e.g.${SKBUILD_DATA_DIR}/foo) targets that wheel tree instead of the platlib, matching theSKBUILD_*_DIRCMake cache variables. Available trees:PLATLIB/PURELIB,DATA,HEADERS,SCRIPTS,METADATA,NULL.Changed in version 1.0: Added the
${SKBUILD_<TREE>_DIR}prefix for targeting wheel trees.Warning
EXPERIMENTAL A leading-slash absolute path (
/platlib,/data,/headers,/scripts, …) is the deprecated spelling of the${SKBUILD_<TREE>_DIR}form and is one level higher than the platlib root.
- license_files: List[str] | None = None¶
A list of license files to include in the wheel. Supports glob patterns.
The default is
["LICEN[CS]E*", "COPYING*", "NOTICE*", "AUTHORS*"].Warning
Must not be set if
project.license-filesis set.
- packages: List[str] | Dict[str, str] | None = None¶
A list of packages to auto-copy into the wheel.
If this is not set, it will default to the first of
src/<package>,python/<package>, or<package>if they exist. The prefix(s) will be stripped from the package name inside the wheel.An entry may also point at a single module file (e.g.
hello.py), which is copied in as a top-level module rather than a package directory.If a dict, provides a mapping of package name to source directory.
Changed in version 1.0: An entry may point at a single module file.
- platlib: bool | None = None¶
Target the platlib or the purelib.
If not set, the default is to target the platlib if
wheel.cmakeistrue, and the purelib otherwise.
- py_api: str = ''¶
The Python version tag used in the wheel file.
The default (empty string) will use the default Python version.
You can also set this to “cp38” to enable the CPython 3.8+ Stable ABI / Limited API (only on CPython and if the version is sufficient, otherwise this has no effect). For free-threaded Python, you can use “cp315t” to enable the free-threaded stable ABI (only on CPython free-threaded builds and if the version is sufficient). You can request both with “cp315.cp315t”. On a free-threaded build this emits a combined “cp315-abi3.abi3t” tag: abi3t is a subset of abi3 (PEP 803), so the single free-threaded binary also loads under a GIL-enabled CPython 3.15+. On a GIL build only abi3 can be produced, so it falls back to “cp315-abi3”. The combined tag shares one minor version, so the classic abi3 minor must not be newer than the free-threaded one (e.g. “cp316.cp315t” is rejected). Or you can set it to “py3” or “py2.py3” to ignore Python ABI compatibility. The ABI tag is inferred from this tag.
This value is used to construct
SKBUILD_SABI_COMPONENTCMake variable.Changed in version 1.0: Added the free-threaded stable ABI (“cp315t”) and the combined abi3.abi3t tag (“cp315.cp315t”).
- reproducible: bool = False¶
Try to build a reproducible wheel.
Unix and Python 3.9+ recommended.
When enabled, archive timestamps and file permissions are normalized, and
SOURCE_DATE_EPOCHis exported to the CMake build (if not already set) so compilers that honor it can produce deterministic output.SOURCE_DATE_EPOCHis used for timestamps if set, or a fixed value if not.Added in version 1.0.
See also
- tags: List[str] | None = None¶
Wheel tags to manually force, {interpreter}-{abi}-{platform} format.
Manually specify the wheel tags to use, ignoring other inputs such as
wheel.py-api. Each tag must be of the format {interpreter}-{abi}-{platform}. If not specified, these tags are automatically calculated. This cannot be set in the static[tool.scikit-build]table; use it in an override, config-settings, or an environment variable.
scikit_build_core.settings.skbuild_overrides module¶
- class scikit_build_core.settings.skbuild_overrides.OverrideRecord(key, original_value, value, passed_all, passed_any)[source]¶
Bases:
objectRecord of the override action.
Saves the original and final values, and the override reasons.
scikit_build_core.settings.skbuild_read_settings module¶
- class scikit_build_core.settings.skbuild_read_settings.SettingsReader(pyproject, config_settings, *, state, extra_settings=None, verify_conf=True, env=None, retry=False)[source]¶
Bases:
object
scikit_build_core.settings.skbuild_schema module¶
scikit_build_core.settings.sources module¶
This module implements the configuration sources used by scikit-build-core.
Each concrete Source adapts one input representation, such as
environment variables, PEP 517 config-settings, or nested TOML tables, into
the same nested dataclass model. SourceChain combines those sources and
applies them in precedence order when building the final settings object.
An end user usually interacts with SourceChain, which takes a
dataclass type and returns an instance with fields populated.
Example:
@dataclasses.dataclass
class ExampleSettings:
generator: str = "Unix Makefiles"
tags: list[str] = dataclasses.field(default_factory=list)
defines: dict[str, str] = dataclasses.field(default_factory=dict)
pyproject = {
"tool": {
"example": {
"generator": "Unix Makefiles",
"defines": {"A": "1"},
}
}
}
env = {"EXAMPLE_TAGS": "fast;docs", "EXAMPLE_DEFINES": "B=2"}
config_settings = {"generator": "Ninja"}
sources = SourceChain(
EnvSource("EXAMPLE", env=env),
ConfSource(settings=config_settings),
TOMLSource("tool", "example", settings=pyproject),
)
settings = sources.convert_target(ExampleSettings)
assert settings.generator == "Ninja"
assert settings.tags == ["fast", "docs"]
assert settings.defines == {"B": "2", "A": "1"}
unrecognized_options = list(sources.unrecognized_options(ExampleSettings))
Naming conventions:
modelis the complete Dataclass.targetis the type to convert a single item to.settingsis the input data source (unless it already has a name, likeenv).optionsare the names of the items in themodel, formatted in the style of the current Source.fieldsare the tuple of strings describing a nested field in themodel.
Source representations:
EnvSource: reads values in environment variables. Lists are encoded as"a;b"and dicts as"key=value;other=value".ConfSource: reads values in a flat mapping keyed by dotted option names from the command line, like-Ca.b=c.TOMLSource: reads values in a nested TOML mapping, like inpyproject.toml.SourceChain: queries sources in order and asks the first matching source to convert its native value into the requested dataclass field type.
When setting up your dataclasses, these types are handled:
str: A string type, nothing special.bool: Supports bool in TOML, not handled in envvar/config (so only useful in a Union)Any callable (Path, Version): Passed the string input.
Optional[T]: Treated like T. Default should be None, since no input format supports None’s.Union[str, ...]: Supports other input types in TOML form (bool currently). Otherwise a string.Union[str, List[str]]: A single string, or a list (a repeated option in config form,;separated in EnvVar/config forms, or native in TOML).List[T]: A list of items. ; separated supported in EnvVar/config forms. T can be a dataclass (TOML only).Dict[str, T]: A table of items. TOML supports a layer of nesting. Any is supported as an item type.Union[list[T], Dict[str, T]](TOML only): A list or dict of items.Literal[...]: A list of strings, the result must be in the list.Annotated[Dict[...], "EnvVar"]: A dict of items, where each item can be a string or a dict with “env” and “default” keys.
These are supported for JSON schema generation for the TOML, as well.
Integers/floats would be easy to add, but haven’t been needed yet.
- class scikit_build_core.settings.sources.ConfSource(*prefixes, settings, verify=True)[source]¶
Bases:
SourceSource for PEP 517
config-settings.While most mechanisms (pip, uv, build) only support text, gpep517 allows an arbitrary json input, so this currently also handles bools.
Example:
source = ConfSource( "skbuild", settings={ "skbuild.logging.level": "DEBUG", "skbuild.cmake.define.CMAKE_CXX_STANDARD": "20", }, ) assert source.get_item("logging", "level", is_dict=False) == "DEBUG" assert source.get_item("cmake", "define", is_dict=True) == { "CMAKE_CXX_STANDARD": "20" }
- all_option_names(target)[source]¶
Given a model, produce a list of all possible names (used for producing suggestions).
- classmethod convert(item, target)[source]¶
Convert a source-native
iteminto the requestedtargettype.Raises
TypeErrorif the conversion fails.- Return type:
- get_item(*fields, is_dict)[source]¶
Return the source-native value for a field path.
The return type depends on the source: env returns a raw string, config-settings returns a string/list/bool or reconstructed dict, and TOML returns the native TOML object. Raises
KeyErrorif the value is missing.is_dictis set for dict-typed targets, because some sources represent dict entries as nested keys.
- has_item(*fields, is_dict)[source]¶
Check whether the source contains a field path.
For example,
fields=("a", "b")asks whether the source has a value for the nested model fielda.b.is_dictis set for dict-typed targets, because some sources represent dict entries as nested keys.- Return type:
- settings: Mapping[str, str | list[str] | bool]¶
Flat backend
config-settingsmapping keyed by dotted option names.Scalar values are stored directly. Dict-typed target fields are represented by multiple flat entries such as
"sdist.include.foo" = "bar".
- class scikit_build_core.settings.sources.EnvSource(prefix, *, env=None)[source]¶
Bases:
SourceSource backed by environment variables.
Nested field paths are represented by uppercased underscore-separated names such as
PREFIX_A_B. Values remain raw strings in the environment until they are converted into the requested field type.Example:
env = { "SKBUILD_CMAKE_ARGS": "-GNinja;-DCMAKE_BUILD_TYPE=Debug", "SKBUILD_CMAKE_DEFINE": "CMAKE_CXX_STANDARD=20;BUILD_TESTING=OFF", } source = EnvSource("SKBUILD", env=env) assert source.get_item("cmake", "args", is_dict=False) == ( "-GNinja;-DCMAKE_BUILD_TYPE=Debug" ) assert source.get_item("cmake", "define", is_dict=False) == ( "CMAKE_CXX_STANDARD=20;BUILD_TESTING=OFF" )
- all_option_names(target)[source]¶
Given a model, produce a list of all possible names (used for producing suggestions).
- classmethod convert(item, target)[source]¶
Convert an item from the environment (always a string) into a target type.
- Return type:
- get_item(*fields, is_dict)[source]¶
Return the source-native value for a field path.
The return type depends on the source: env returns a raw string, config-settings returns a string/list/bool or reconstructed dict, and TOML returns the native TOML object. Raises
KeyErrorif the value is missing.is_dictis set for dict-typed targets, because some sources represent dict entries as nested keys.
- class scikit_build_core.settings.sources.Source(*args, **kwargs)[source]¶
Bases:
Protocol- all_option_names(target)[source]¶
Given a model, produce a list of all possible names (used for producing suggestions).
- classmethod convert(item, target)[source]¶
Convert a source-native
iteminto the requestedtargettype.Raises
TypeErrorif the conversion fails.- Return type:
- get_item(*fields, is_dict)[source]¶
Return the source-native value for a field path.
The return type depends on the source: env returns a raw string, config-settings returns a string/list/bool or reconstructed dict, and TOML returns the native TOML object. Raises
KeyErrorif the value is missing.is_dictis set for dict-typed targets, because some sources represent dict entries as nested keys.- Return type:
- class scikit_build_core.settings.sources.SourceChain(*sources, prefixes=())[source]¶
Bases:
object- convert_target(target, *prefixes)[source]¶
Build a dataclass instance from the chained sources.
For each field, this first asks each source whether it has a native value for the current path. The first matching source returns that raw value via
get_item, and that same source then normalizes it withconvertinto the dataclass field type. Nested dataclasses recurse intoconvert_target. Dict fields are special: later sources extend the dict assembled so far instead of replacing it outright.Example:
@dataclasses.dataclass class Example: tags: list[str] = dataclasses.field(default_factory=list) defines: dict[str, str] = dataclasses.field(default_factory=dict) chain = SourceChain( EnvSource("EXAMPLE", env={"EXAMPLE_DEFINES": "A=1"}), ConfSource(settings={"tags": ["from-conf"]}), TOMLSource(settings={"tags": ["from-toml"], "defines": {"B": "2"}}), ) settings = chain.convert_target(Example) assert settings.tags == ["from-conf"] assert settings.defines == {"A": "1", "B": "2"}
- Return type:
TypeVar(T)
- class scikit_build_core.settings.sources.TOMLSource(*prefixes, settings)[source]¶
Bases:
SourceSource backed by a nested TOML mapping.
After applying any constructor prefixes,
self.settingsis the nested table for that subtree.get_itemreturns the native TOML value found at the requested field path, andconvertturns that TOML value into the target dataclass field type.Example:
source = TOMLSource( "tool", "scikit-build", settings={ "tool": { "scikit-build": { "wheel": {"packages": ["src/example"]}, } } }, ) assert source.get_item("wheel", "packages", is_dict=False) == ["src/example"]
- all_option_names(target)[source]¶
Given a model, produce a list of all possible names (used for producing suggestions).
- classmethod convert(item, target)[source]¶
Convert an
itemfrom TOML into atargettype.- Return type:
- get_item(*fields, is_dict)[source]¶
Return the source-native value for a field path.
The return type depends on the source: env returns a raw string, config-settings returns a string/list/bool or reconstructed dict, and TOML returns the native TOML object. Raises
KeyErrorif the value is missing.is_dictis set for dict-typed targets, because some sources represent dict entries as nested keys.- Return type: