Custom .pth in dev mode with relative paths

[schussda]

I have a custom .pth file that needs to be installed in order for the project to work (imports). I cant change the imports because they are also at the user side of this legacy project.

=> Some sub directories of the project need to be on python path.

I did this via

[tool.hatch.build.targets.wheel.force-include]
"custom.pth" = "custom.pth"

where

custom.pth:

subdir1/subdir2
...

When the project is installed into site-packages (normal use case) this works. But in dev mode these paths must be absolute.
Can hatch handle this or do you have another idea how to deal with this?

[ofek]

You can create a custom build hook and then set force_include_editable https://hatch.pypa.io/latest/plugins/builder/wheel/#build-data

[schussda]

Thanks i will try this next Week. I was not into the build hooks yet. Great stuff

[schussda]

I implemented the build hook for initialize so that a foo_dev.pth file with absolute paths is created dynamically. This works.
Then i added force_include_editable to pyproject.toml:

[tool.hatch.build.targets.wheel.force-include]
"foo.pth" = "foo.pth"

[tool.hatch.build.targets.wheel.force_include_editable]
"foo_dev.pth" = "foo.pth"

=> I install the project via uv pip install -e PATH inside the shell of another hatch project
=> wheel.force-include is always used, wheel.force_include_editable is ignored, what i am may doing wrong?

edit:
I tried patching the build_data["force_include"] in the initialize method. This works with pip but with uv the .pth file is messed up, looks like uv does things concurrently => .pth file is a mixture of both "foo.pth" and "foo_dev.pth"

edit2:
I changed it so just build_data["force_include_editable"] is set in initialize hook, this works!
But setting [tool.hatch.build.targets.wheel.force_include_editable] in the pyproject.toml doesnt work for me