Convert to hatch and pyproject.toml

[nicoddemus]

• Converted setup.py to pyproject.toml: used hatch new --init and manually added hatch-vcs configuration.

• Updated hynek/build-and-inspect-python-package -- in the end this was the original problem.

• Added dependabot.yml configuration to avoid this problem in the future.

Follow up to #77.

[RonnyPfannschmidt]

Let's completely switch over something is getting confused

[nicoddemus]

Does anybody know of a tool that can do that automatically? Not looking forward to it manually. 😁

[RonnyPfannschmidt]

https://www.pyopensci.org/python-package-guide/tutorials/setup-py-to-pyproject-toml.html

[RonnyPfannschmidt]

imho this is fine to go to hatch :)

[RonnyPfannschmidt]

@nicoddemus i can do it sometime tommorow if you dont get to it today

[Pierre-Sassoulas]

It's also possible to do a migration to setup.cfg first, then use an ini to toml conversion, it's two steps but historically it make sense. (I can do it too if you want)

[RonnyPfannschmidt]

@Pierre-Sassoulas why do 2 step when 1 step tools are avaliable?

[nicoddemus]

Thanks @RonnyPfannschmidt for the tip!

Hmmm still failing... weird, it worked just fine for me locally:

• dist\pytest_reportlog-0.4.1.dev40+g3c5a7b2.d20250805.tar.gz
• dist\pytest_reportlog-0.4.1.dev40+g3c5a7b2.d20250805-py3-none-any.whl

I used hatch build and python -m build, both generated commands generated releases 0.4.1.dev*.

[RonnyPfannschmidt]

I suspect cache poisoning

[nicoddemus]

Created another job which builds the package manually and it passes: https://github.com/pytest-dev/pytest-reportlog/actions/runs/16763542482/job/47464059761?pr=78

Seems related to hynek/build-and-inspect-python-package... updating it.

[nicoddemus]

💥 it was just a matter of updating hynek/build-and-inspect-python-package then.

[Pierre-Sassoulas]

It permits to not have to learn another tool if like me you already did multiple setup.cfg migration before :) (and hatch need some cleanup to reinstate something simple and stupid like setuptools at the end). Or we can keep hatch but the python packaging ecosystem would benefit from less choice imo.

[Pierre-Sassoulas]

We don't have to keep hatch it was only for the migration, right ?

[RonnyPfannschmidt]

Actually keeping it us nice for pure python its much nicer than setuptools

And its way easier to maintain

[nicoddemus]

Thanks folks!