In my Python project, I use the library just_playback as a dependency. When I'm on my development machine, I just fetch the library from PyPI and it works like a charm. However, the client I'm developing for can't use that particular artifact, because it's built for other processors than my client uses. The library has to be built from source on the client's hardware (I have tested this and it works).
Is it possible to direct the building of my dependency from source instead of fetching it from PyPI, before building my own project, and within my own pyproject.toml?
One possible workaround I thought of and tried to look for in the pyproject.toml manual is to define the just_playback depencency as supplied, so that the source code expects the library to be there, but nothing is installed if it's not there, like one can do in Java, for example. I couldn't find any information on that, though, so I assume that's not an option.
I build the project using hatchling and the client uses pip to install it, if that's helpful information.
Thanks to comments to my question, I found a solution that satisfied my requirements.
I ended up writing the following in the requirements.txt file:
--no-binary just_playback~=0.1.8
just_playback~=0.1.8
And installing it with pip like this:
pip install -r requirements.txt .