-
Notifications
You must be signed in to change notification settings - Fork 2
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
Consider moving to a PEP665 compliant build and packaging tool #93
Comments
I believe Poetry is working towards support in Poetry 2.0. Depending on your needs, Hatch and PDM are probably the next most popular workflow tools. |
See Switching to Hatch by @oliverandrich |
I found this issue linked via hatch and figured I'd drop in with a shameless plug (hope you don't mind 😃) for my hatch plugin, hatch-pip-compile. It enables lockfile support for hatch via pip-compile or uv and has allowed hatch to be a complete one-stop-shop for all my Python project management needs. If you're considering hatch but uncertain about its lack of lockfile support hatch-pip-compile might just be what you're waiting for. Cheers! |
Hey @juftin thanks for the shameless plug 😄 I started doing an initial migration to Found your blog post and will study the tool and hopefully it tips us over to move to Thanks for taking the time to comment on this issue. |
Is your feature request related to a problem? Please describe.
We've been using
poetry
as our package management tool which works well for all our needs. Initially I had wondered what other major projects used for package management (moving fromsetuptools
in theprestans
days).Looking under the hood of projects like
fastapi
I found they all use hatch.@brettcannon started the issue Interested in supporting PEP 665? on the repository and it would seem that there are major design variations which would it difficult to make
poetry
compatible withpep665
(note that there's mention of the work being sponsored)The python packaging site refers to
hatch
quite strongly.Describe the solution you'd like
We should thoroughly read through the packaging guide to ensure we have the right structures and flows.
We should identify if
poetry
is still a suitable tool for the requirements, and if not what is and why?We should then produce:
Dockerfile
for building the packages for development and productionDescribe alternatives you've considered
NA
Additional context
See the Python packaging guide.
The text was updated successfully, but these errors were encountered: