Use pyproject.toml

[bkmgit]

Closes #107

[bkmgit]

@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]

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]

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.

[bkmgit]

• Dst Reader Thread values EmbroidePy/pyembroidery#149
• please rename master branch to main EmbroidePy/pyembroidery#157
• Add a pyproject.toml file EmbroidePy/pyembroidery#182

[kaalleen]

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.

[kaalleen]

@bkmgit I rebased our pyembroidery on upstream.
I think this is when you can take action for file structure changes necessary to place it on pypi.
Not sure if you want to rebase your branch or create a new one.