Skip to content
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

Use pyproject.toml #110

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Use pyproject.toml #110

wants to merge 1 commit into from

Conversation

bkmgit
Copy link

@bkmgit bkmgit commented Mar 10, 2025

Closes #107

@bkmgit
Copy link
Author

bkmgit commented Mar 10, 2025

@kaalleen Any preference on build backend? Hatchling, setuptools or PDM are reasonable choices:
https://packaging.python.org/en/latest/tutorials/packaging-projects/#choosing-a-build-backend

@kaalleen
Copy link
Collaborator

I think we were using setuptools so far. Maybe that.
But since I have no idea about these things, I don't really have a preference. So if you prefer one over an other, you could convince me quickly.

@bkmgit
Copy link
Author

bkmgit commented Mar 11, 2025

Hatchling and PDM offer ability to build C/C++ dependencies. They may make it easier for new contributors. uv is also gaining popularity, though it is built using rust, review of rust dependencies is not great. Scientific python ecosystem promotes Hatchling at present, will check if any can simplify build process for Ink/Stitch.

Maybe upstream pyembroidery has an opinion, there is a possibility of keeping the projects compatible/combining.

@kaalleen
Copy link
Collaborator

Maybe upstream pyembroidery has an opinion, there is a possibility of keeping the projects compatible/combining.

Yes, good idea. I really would want them to stay compatible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build using pyproject.toml
2 participants