partial-pixi.json
Pixi configuration for pyproject.toml
Validate with Lintel
npx @lintel/lintel checkThe [tool.pixi] section of a pyproject.toml.
Properties
A description of steps performed when an environment is activated
2 nested properties
A map of environment variables to values, used in the activation of the environment. These will be set in the shell. Thus these variables are shell specific. Using '$' might not expand to a value in different shells.
The scripts to run when the environment is activated
The build conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The conda version constraints. These constrain the versions of packages that may be installed without explicitly requiring them. If the package is installed as a dependency of another package, it must satisfy these constraints.
The conda dependencies, consisting of a package name and a requirement in MatchSpec format
Source packages whose dependencies should be installed without building the package itself. Useful for development environments.
The environments of the project, defined as a full object or a list of feature names.
The features of the project
The host conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The package's metadata information.
15 nested properties
6 nested properties
19 nested properties
Additional dependencies to install alongside the build backend
A git branch to use
The build string of the package
The build number of the package, can be a spec like >=1 or <=10 or 1
The channel the packages needs to be fetched from
The conda channels that are used to fetch the build backend from
The file name of the package
The git URL to the repo
The license of the package
The md5 hash of the package
The name of the build backend package
The path to the package
A git SHA revision to use
The sha256 hash of the package
The subdir of the package, also known as platform
A subdirectory to use in the repo
A git tag to use
The URL to the package
Additional dependencies to install alongside the build backend
The conda channels that are used to fetch the build backend from
The configuration of the build backend
The location of a package's source code.
6 nested properties
A git branch to use
The git URL to the source repo
The path to the source
A git SHA revision to use
A subdirectory to use in the repo
A git tag to use
Target-specific build configuration for different platforms
The authors of the project. Can be a list of strings or { workspace = true } to inherit from workspace
The build conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
A short description of the project. Can be a string or { workspace = true } to inherit from workspace
The URL of the documentation of the project. Can be a URL or { workspace = true } to inherit from workspace
The URL of the homepage of the project. Can be a URL or { workspace = true } to inherit from workspace
The host conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The license of the project; we advise using an SPDX identifier. Can be a string or { workspace = true } to inherit from workspace
The path to the license file of the project. Can be a path or { workspace = true } to inherit from workspace
The name of the package. Can be a string or { workspace = true } to inherit from workspace
The path to the readme file of the project. Can be a path or { workspace = true } to inherit from workspace
The URL of the repository of the project. Can be a URL or { workspace = true } to inherit from workspace
The conda dependencies required at runtime. See https://pixi.sh/latest/build/dependency_types/ for more information.
Machine-specific aspects of the package
The version of the project; we advise use of SemVer. Can be a string or { workspace = true } to inherit from workspace
The project's metadata information.
23 nested properties
The conda channels that can be used in the project. Unless overridden by priority, the first channel listed will be preferred.
The authors of the project
The build variants of the project
Ordered list of variant definition files.
The priority of the channel.
The conda to PyPI mapping configuration
A short description of the project
The URL of the documentation of the project
Exclude any package newer than this date
The URL of the homepage of the project
The path to the license file of the project
The name of the project; we advise use of the name of the repository
The platforms that the project supports
Defines the enabling of preview features of the project
Options that determine the behavior of PyPI package resolution and installation
10 nested properties
A list of PyPI dependencies that override the resolved dependencies
Additional PyPI registries that should be used as extra indexes
Paths to directory containing
The strategy to use when resolving packages from multiple indexes
PyPI registry that should be used as the primary index
Don't use pre-built wheels for these packages
Packages that should NOT be built
Packages that should NOT be isolated during the build process
The strategy to use when considering pre-release versions
Skip wheel filename validation, allowing installation of wheels with version mismatches between filename and metadata
The path to the readme file of the project
The URL of the repository of the project
The required version spec for pixi itself to resolve and build the project.
Options related to S3 for this project
The strategy used to solve packages.
The workspace targets
The PyPI dependencies
Options that determine the behavior of PyPI package resolution and installation
10 nested properties
A list of PyPI dependencies that override the resolved dependencies
Additional PyPI registries that should be used as extra indexes
Paths to directory containing
The strategy to use when resolving packages from multiple indexes
PyPI registry that should be used as the primary index
Don't use pre-built wheels for these packages
Packages that should NOT be built
Packages that should NOT be isolated during the build process
The strategy to use when considering pre-release versions
Skip wheel filename validation, allowing installation of wheels with version mismatches between filename and metadata
Platform-specific requirements
6 nested properties
The architecture the project supports
The minimum version of CUDA
The minimum version of libc
The minimum version of the Linux kernel
The minimum version of MacOS
Whether the project supports UNIX
The targets of the project
The tasks of the project
Third-party tool configurations, ignored by pixi
The project's metadata information.
23 nested properties
The conda channels that can be used in the project. Unless overridden by priority, the first channel listed will be preferred.
The authors of the project
The build variants of the project
Ordered list of variant definition files.
The priority of the channel.
The conda to PyPI mapping configuration
A short description of the project
The URL of the documentation of the project
Exclude any package newer than this date
The URL of the homepage of the project
The path to the license file of the project
The name of the project; we advise use of the name of the repository
The platforms that the project supports
Defines the enabling of preview features of the project
Options that determine the behavior of PyPI package resolution and installation
10 nested properties
A list of PyPI dependencies that override the resolved dependencies
Additional PyPI registries that should be used as extra indexes
Paths to directory containing
The strategy to use when resolving packages from multiple indexes
PyPI registry that should be used as the primary index
Don't use pre-built wheels for these packages
Packages that should NOT be built
Packages that should NOT be isolated during the build process
The strategy to use when considering pre-release versions
Skip wheel filename validation, allowing installation of wheels with version mismatches between filename and metadata
The path to the readme file of the project
The URL of the repository of the project
The required version spec for pixi itself to resolve and build the project.
Options related to S3 for this project
The strategy used to solve packages.
The workspace targets
Definitions
A description of steps performed when an environment is activated
A map of environment variables to values, used in the activation of the environment. These will be set in the shell. Thus these variables are shell specific. Using '$' might not expand to a value in different shells.
The scripts to run when the environment is activated
19 nested properties
Additional dependencies to install alongside the build backend
A git branch to use
The build string of the package
The build number of the package, can be a spec like >=1 or <=10 or 1
The channel the packages needs to be fetched from
The conda channels that are used to fetch the build backend from
The file name of the package
The git URL to the repo
The license of the package
The md5 hash of the package
The name of the build backend package
The path to the package
A git SHA revision to use
The sha256 hash of the package
The subdir of the package, also known as platform
A subdirectory to use in the repo
A git tag to use
The URL to the package
Additional dependencies to install alongside the build backend
The conda channels that are used to fetch the build backend from
The configuration of the build backend
The location of a package's source code.
6 nested properties
A git branch to use
The git URL to the source repo
The path to the source
A git SHA revision to use
A subdirectory to use in the repo
A git tag to use
Target-specific build configuration for different platforms
Additional dependencies to install alongside the build backend
A git branch to use
The build string of the package
The build number of the package, can be a spec like >=1 or <=10 or 1
The channel the packages needs to be fetched from
The conda channels that are used to fetch the build backend from
The file name of the package
The git URL to the repo
The license of the package
The md5 hash of the package
The name of the build backend package
The path to the package
A git SHA revision to use
The sha256 hash of the package
The subdir of the package, also known as platform
A subdirectory to use in the repo
A git tag to use
The URL to the package
Target-specific build configuration for different platforms
Target-specific configuration for the build backend
A precise description of a conda channel, with an optional priority.
The channel the packages needs to be fetched from
The priority of the channel
The priority of the channel.
The dependencies of a task.
the name of the task to depend on
The (positional or named) arguments to pass to the task
The environment to use for the task
A composition of the dependencies of features which can be activated to run tasks or provide a shell
The features that define the environment
Whether to add the default feature to this environment
The group name for environments that should be solved together
A composable aspect of the project which can contribute dependencies and tasks to an environment
A description of steps performed when an environment is activated
2 nested properties
A map of environment variables to values, used in the activation of the environment. These will be set in the shell. Thus these variables are shell specific. Using '$' might not expand to a value in different shells.
The scripts to run when the environment is activated
The build conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The priority of the channel.
The conda channels that can be considered when solving environments containing this feature
The conda version constraints. These constrain the versions of packages that may be installed without explicitly requiring them. If the package is installed as a dependency of another package, it must satisfy these constraints.
The conda dependencies, consisting of a package name and a requirement in MatchSpec format
Source packages whose dependencies should be installed without building the package itself. Useful for development environments.
The host conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The platforms that the feature supports: a union of all features combined in one environment is used for the environment.
The PyPI dependencies of this feature
Options that determine the behavior of PyPI package resolution and installation
10 nested properties
A list of PyPI dependencies that override the resolved dependencies
Additional PyPI registries that should be used as extra indexes
Paths to directory containing
The strategy to use when resolving packages from multiple indexes
PyPI registry that should be used as the primary index
Don't use pre-built wheels for these packages
Packages that should NOT be built
Packages that should NOT be isolated during the build process
The strategy to use when considering pre-release versions
Skip wheel filename validation, allowing installation of wheels with version mismatches between filename and metadata
The strategy used to solve packages.
Platform-specific requirements
6 nested properties
The architecture the project supports
The minimum version of CUDA
The minimum version of libc
The minimum version of the Linux kernel
The minimum version of MacOS
Whether the project supports UNIX
Machine-specific aspects of this feature
The tasks provided by this feature
The path to the directory containing packages
Path to the directory of packages
The URL to the html file containing href-links to packages
URL to html file with href-links to packages
The family of the libc
The version of libc
A precise description of a conda package version.
A git branch to use
The build string of the package
The build number of the package, can be a spec like >=1 or <=10 or 1
The channel the packages needs to be fetched from
The file name of the package
The git URL to the repo
The license of the package
The md5 hash of the package
The path to the package
A git SHA revision to use
The sha256 hash of the package
The subdir of the package, also known as platform
A subdirectory to use in the repo
A git tag to use
The URL to the package
The package's metadata information.
6 nested properties
19 nested properties
Additional dependencies to install alongside the build backend
A git branch to use
The build string of the package
The build number of the package, can be a spec like >=1 or <=10 or 1
The channel the packages needs to be fetched from
The conda channels that are used to fetch the build backend from
The file name of the package
The git URL to the repo
The license of the package
The md5 hash of the package
The name of the build backend package
The path to the package
A git SHA revision to use
The sha256 hash of the package
The subdir of the package, also known as platform
A subdirectory to use in the repo
A git tag to use
The URL to the package
Additional dependencies to install alongside the build backend
The conda channels that are used to fetch the build backend from
The configuration of the build backend
The location of a package's source code.
6 nested properties
A git branch to use
The git URL to the source repo
The path to the source
A git SHA revision to use
A subdirectory to use in the repo
A git tag to use
Target-specific build configuration for different platforms
The authors of the project. Can be a list of strings or { workspace = true } to inherit from workspace
The build conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
A short description of the project. Can be a string or { workspace = true } to inherit from workspace
The URL of the documentation of the project. Can be a URL or { workspace = true } to inherit from workspace
The URL of the homepage of the project. Can be a URL or { workspace = true } to inherit from workspace
The host conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The license of the project; we advise using an SPDX identifier. Can be a string or { workspace = true } to inherit from workspace
The path to the license file of the project. Can be a path or { workspace = true } to inherit from workspace
The name of the package. Can be a string or { workspace = true } to inherit from workspace
The path to the readme file of the project. Can be a path or { workspace = true } to inherit from workspace
The URL of the repository of the project. Can be a URL or { workspace = true } to inherit from workspace
The conda dependencies required at runtime. See https://pixi.sh/latest/build/dependency_types/ for more information.
Machine-specific aspects of the package
The version of the project; we advise use of SemVer. Can be a string or { workspace = true } to inherit from workspace
A supported operating system and processor architecture pair.
A git branch to use
The PEP 508 extras of the package
The subdirectory in the repo, a path from the root of the repo.
The PEP 508 extras of the package
A git SHA revision to use
The subdirectory in the repo, a path from the root of the repo.
The PEP 508 extras of the package
The subdirectory in the repo, a path from the root of the repo.
A git tag to use
Options that determine the behavior of PyPI package resolution and installation
A list of PyPI dependencies that override the resolved dependencies
Additional PyPI registries that should be used as extra indexes
Paths to directory containing
The strategy to use when resolving packages from multiple indexes
PyPI registry that should be used as the primary index
Don't use pre-built wheels for these packages
Packages that should NOT be built
Packages that should NOT be isolated during the build process
The strategy to use when considering pre-release versions
Skip wheel filename validation, allowing installation of wheels with version mismatches between filename and metadata
If true the package will be installed as editable
The PEP 508 extras of the package
A path to a local source or wheel
The subdirectory in the repo, a path from the root of the repo.
The PEP 508 extras of the package
A URL to a remote source or wheel
The PEP 508 extras of the package
The index to fetch the package from
Options related to S3 for this project
The endpoint URL to use for the S3 client
Whether to force path style for the S3 client
The region to use for the S3 client
The strategy used to solve packages.
The location of a package's source code.
A git branch to use
The git URL to the source repo
The path to the source
A git SHA revision to use
A subdirectory to use in the repo
A git tag to use
A precise description of a source package location.
A git branch to use
The git URL to the source repo
The md5 hash of the source package
The path to the source package
A git SHA revision to use
The sha256 hash of the source package
A subdirectory to use in the repo
A git tag to use
The URL to the source package
Platform-specific requirements
The architecture the project supports
The minimum version of CUDA
The minimum version of libc
The minimum version of the Linux kernel
The minimum version of MacOS
Whether the project supports UNIX
A machine-specific configuration of dependencies and tasks
A description of steps performed when an environment is activated
2 nested properties
A map of environment variables to values, used in the activation of the environment. These will be set in the shell. Thus these variables are shell specific. Using '$' might not expand to a value in different shells.
The scripts to run when the environment is activated
The build conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The conda version constraints. These constrain the versions of packages that may be installed without explicitly requiring them. If the package is installed as a dependency of another package, it must satisfy these constraints.
The conda dependencies, consisting of a package name and a requirement in MatchSpec format
Source packages whose dependencies should be installed without building the package itself. Useful for development environments.
The host conda dependencies, used in the build process. See https://pixi.sh/latest/build/dependency_types/ for more information.
The PyPI dependencies for this target
The tasks of the target
The arguments of a task.
The name of the argument
Allowed values for the argument
The default value of the argument
A precise definition of a task.
The arguments to a task
Whether to run in a clean environment, removing all environment variables except those defined in env and by pixi itself.
A shell command to run the task in the limited, but cross-platform bash-like deno_task_shell. See the documentation for supported syntax
The working directory to run the task
A default environment to run the task
The tasks that this task depends on. Environment variables will not be expanded.
The tasks that this task depends on. Environment variables will not be expanded. Deprecated in favor of depends-on from v0.21.0 onward.
A short description of the task
A map of environment variables to values, used in the task, these will be overwritten by the shell.
A list of .gitignore-style glob patterns that should be watched for changes before this command is run. Environment variables will be expanded.
A list of .gitignore-style glob patterns that are generated by this command. Environment variables will be expanded.
The project's metadata information.
The conda channels that can be used in the project. Unless overridden by priority, the first channel listed will be preferred.
The authors of the project
The build variants of the project
Ordered list of variant definition files.
The priority of the channel.
The conda to PyPI mapping configuration
A short description of the project
The URL of the documentation of the project
Exclude any package newer than this date
The URL of the homepage of the project
The path to the license file of the project
The name of the project; we advise use of the name of the repository
The platforms that the project supports
Defines the enabling of preview features of the project
Options that determine the behavior of PyPI package resolution and installation
10 nested properties
A list of PyPI dependencies that override the resolved dependencies
Additional PyPI registries that should be used as extra indexes
Paths to directory containing
The strategy to use when resolving packages from multiple indexes
PyPI registry that should be used as the primary index
Don't use pre-built wheels for these packages
Packages that should NOT be built
Packages that should NOT be isolated during the build process
The strategy to use when considering pre-release versions
Skip wheel filename validation, allowing installation of wheels with version mismatches between filename and metadata
The path to the readme file of the project
The URL of the repository of the project
The required version spec for pixi itself to resolve and build the project.
Options related to S3 for this project
The strategy used to solve packages.
The workspace targets
Indicates that a field should inherit its value from the workspace.
Must be true to inherit from workspace
Target-specific configuration for a workspace
The build variants for this workspace target