-
-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let hatch build
support non-hatchling backends?
#507
Comments
This I've thought about but it would be an extraordinary amount of effort when one could just do: [envs.build]
detached = true
dependencies = ["build"]
[envs.build.scripts]
all = "python -m build"
sdist = "python -m build --sdist"
wheel = "python -m build --wheel" |
I saw some discussion at pyOpenSci/python-package-guide#55 (or maybe part 1, can't remember) about Hatch considering supporting other backends. Is that option still on the table? If so, maybe worth reopening this issue? |
Yes I will do this for the next release |
Is this still in the cards? |
Thanks for following up! This has been supported for a few months now https://hatch.pypa.io/latest/history/hatch/#hatch-v1.8.0 |
This is more of a discussion than a feature-request for now.
Is there a strong reason for requiring
hatch build
only supporthatchling
? Although hatch acknowledges that users might prefer to use only the build-backend from hatch, it's also possible that users would want to go the other direction - use hatch to manage their environments, but not build. From a cursory glance of the source code, I couldn't see any strong indication that we could not do this.Looking forward to your comments!
The text was updated successfully, but these errors were encountered: