Move builds to pyproject.toml while keeping setuptools in place

[Jakeroid]

To proceed with building the system, we should simplify the process. However, we want to avoid introducing new abstractions like poetry. Therefore, we should consider adopting pyproject.toml.

[Jakeroid]

A related issues:

#205

[iloveitaly]

@Jakeroid wdyt about moving to uv + uv_build? The test folder is still being included in the wheel and I'm not sure why. I'm not too familiar with the older package management system in Python and I'm not able to fully reproduce the issues locally.

I can submit a PR to move everything over to UV if you'd be cool with it.

[Jakeroid]

@iloveitaly

Thank you for taking a look. In general, the less friction we have, the better. UV is kind of a new tool. Will it still be around in 5 years? I don't know.

It would be nice to solve that without changing setuptools for UV.

What do you think?

[eirnym]

Scripts:

testing

Run tests with just pytest. tox tool will improve running and testing on various python versions. Optionally, add additional configuration to pyproject.toml

publishing

it's basically a shell script, I'd move to GitHub CI with following separate jobs (to minimize potential secrets leaking). First two could be joined together, third should be in a privileged environment with maintainer verification.

1. test with pytest
2. build dist & sdist
3. twine upload

[donn-chadh]

Hi @Jakeroid, I'd like to take a look at this issue and migrate the build config to pyproject.toml if it's still open. Could you assign it to me? Thanks!