[Question] Why is a "force included" package not deployed from sdist?
See original GitHub issueHi @ofek et al.,
I hope I’m not off-topic in asking this here. I apologize if I am.
I am using hatch in a project and “force including” a package from a directory outside the project’s directory like so:
[tool.hatch.build.force-include]
"../../Utils/Aws" = "Utils/AWS"
When I build my project with hatch build -t sdist
I can see that the files in the above directory are included in the .tar.gz
file alongside my project’s code directory.
However, when I install the .tar.gz
using pip like so: pip install my-package.tar.gz --no-deps
I find that my code fails when trying to import the Utils.AWS
package. Having peeked in Lib/site-packages
I can’t find the Utils directory there.
Am I missing something when building the .tar.gz.
or in how I setup pyproject.toml
?
Thanks, @urig
PS - I’ve noticed that the .tar.gz.
file does not contain an “egg-info” directory with its SOURCES.txt
file. Could this be related to my issue?
Issue Analytics
- State:
- Created a year ago
- Comments:11
Sorry. Will verify tomorrow morning and report.
Ah I see, this only affects dev mode/editable installations. I’ll fix