build directories per target version?

[gwdekker]

Hello! I am trying to use hatch in a monorepo environment. In the monorepo, i will have a folder libraries/my_lib. This library is used across my projects, for example in projects/my_project.

Now, I want to be able to do the following:

1. when developing locally, I want my_lib to be available as an editable package to my_project.
2. I also want to be able to run my_project in production, where I would need a normal wheel of my_lib

I have solved use case 1 in the following way:

• in my_libs pyproject.toml I define:

[tool.hatch.build]
directory = '../.wheels'

[tool.hatch.build.targets.wheel]
versions = ['editable']

Then, in my_project pyproject.toml I can declare my_lib as a dependency, use pip compile to generate a lock file (with argument --find-links /.wheels), and all seems well.

However, as this creates a .whl with only symlinks, it would not work out of the box to ship these wheels into my dockerfile for production.

I tried to modify my_libs pyproject.toml like this:

[tool.hatch.build]
directory = '../.wheels'

[tool.hatch.build.targets.wheel]
versions = ['editable', 'standard']

this seems to build two wheels, but they overwrite each other.

Is there a way to build for these two versions, but save them such that they do not overwrite each other? Either by tweaking the pyproject.toml configuration, or by providing an argument to hatch build that I missed?

It feels I am so close to make this work, but yet so far away... :(

Any help very much appreciated!

[gwdekker]

For completeness: my current workaround is to build the non-editable wheels with the build package, locally installed with pipx: pyproject-build PROJECT_DIR -w -o ./.wheels-for-production