You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently its quite confusing that some things belong to package and the other to the workspace/project. The following specification would be a way to rectify this:
[package]
name = "foobar"version = "0.1.0"
[package.build]
backend = { name = "pixi-build-python", version = "*" }
# Question: should channels also be part of build-backend perhaps?channels = []
# I think this can be achieved in JSON schema if we can match on # `package.build.backend.name` == `pixi-build-python`## Question: Is `args` a good enough name?
[tool.pixi-build-python]
noarch = true
[package.host-dependencies]
python = "3.11"meson-py = "*"
[package.build-dependencies]
cxx-compilers = "*"
[package.run-dependencies]
foobar-ext = "*"
[package.variants]
python = []
# Workspace keys are not nested
[workspace]
[dependencies]
foobar = { source = "." }
[feature]
[environments
[pypi-options]
The text was updated successfully, but these errors were encountered:
Currently its quite confusing that some things belong to package and the other to the workspace/project. The following specification would be a way to rectify this:
The text was updated successfully, but these errors were encountered: