Replies: 1 comment 1 reply
|
The immediate cause is a missing host dependency for the editable build, not the Python 3.13 build environment using a Python 3.12 Hatchling package.
The smallest deterministic fix for this configuration is: [package.host-dependencies]
hatchling = { workspace = true }
editables = "*"Keeping [workspace.dependencies]
editables = "*"
[package.host-dependencies]
hatchling = { workspace = true }
editables = { workspace = true }Then rerun Adding it only to The different Python versions are worth constraining separately if reproducibility requires them to match, but they are not the source of this References: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am working through the pixi-build-python example and have a monorepo with 1 shared lib called common and 2 packages called pipeline_a and pipeline_b. pixi 0.76.1 is the newest version I have access to and I am using it inside of a conda environment. I get the following error running pixi install:
DEBUG ModuleNotFoundError: No module named 'editables'.I highly suspect I misunderstand something about my toml configuration. It will work if I add editables to my workspace dependencies but that doesnt seem like I should be the one specifying it. It seems there are 3 cases:
This is the build config. note that python is 3.13.15 but its using hatchling built for python 3.12 which seems like a problem to me
This is the error message I get when it uses uv to build pipeline-b:
This is my project toml
This is my package toml
This is my package pyproject.toml
All reactions