Project metadata: Remove setup.py. Improve Python compatibility.

[amotl]

Just maintenance while modernizing project metadata: Remove outmoded setup.py, and transfer a few more details to new pyproject.toml.

[seut]

Shouldn't we also add the other supported python versions here?

[amotl]

Thanks. Fixed.

[seut]

Looks good to me, thanks!
Pinging @mfussenegger to ensure we do not miss any feedback on this.

[mfussenegger]

Why do we lower this now? Afaik newer versions intentionally bumped this so that pip install on older python versions would install an old crate-python version - allowing us to drop compat logic for older versions.

[amotl]

setup.py says python_requires=">=3.6", I've just transferred this to pyproject.toml.

[mfussenegger]

This implies that there's now a hatch executable available in $PATH. Looks like this isn't mentioned in DEVELOP.rst - the whole file looks sort of outdated, together with the bootstrap.sh

Can we simplify that, so there's some sort of standard uv venv venv; uv pip install -Ue ".[dev]" with no special custom logic?

[amotl]

Hatch was introduced with GH-739, but updating the files you've mentioned apparently has been missed. Let's track this with a separate ticket so @surister can address it?

[amotl]

I've created a dedicated ticket. Thank you.

• Package: Use standard setuptools or uv build backend #766

[mfussenegger]

Why not fix it? Seems like things are sort of broken as they are in this PR

[amotl]

Seems like things are sort of broken as they are in this PR.

This patch was merely thought cosmetic to remove setup.py as intended. GH-739 already made the project use Hatch, because pyproject.toml takes precedence even when using the traditional setuptools build backend like before. In this spirit, the project would already be broken right now?

Why not fix it?

Switching to setuptools again requires more changes, because standard setuptools uses a different format in pyproject.toml than hatch. Let's discuss here?

[mfussenegger]

Switching to setuptools again requires more changes, because standard setuptools uses a different format in pyproject.toml than hatch. Let's discuss #766 (comment)?

I don't see the advantage of going from A (broken) -> B (this version - also broken) -> C (version that works) when we can do A (broken) -> C (not broken).

Also note that this doesn't require switching away from hatch. It just needs to become a build time dependency that's documented. Could even make use of uvx hatch if we already depend on uv (which should also be documented if that's the case, and isn't mentioned)

[amotl]

Hi. Apologies that I still can't follow what is exactly broken here. Can you share an error message? Hatch is currently a build time dependency, and this works well.

[build-system]
requires = ["hatchling", "versioningit"]
build-backend = "hatchling.build"

[amotl]

I might be seeing the problem now: Is it hatchling vs. hatch? So, let's just add hatch, right! See 8a9a172.