Update Technical Documentation for Python Hatchling Build Method #874

[goessebr]

Issue #874

@koenedaele, @Wim-De-Clercq

Previously, our testing procedure utilized tox, as described in our documentation. However, it has been removed in commit bc77ad5.

We now employ GitHub Actions as our testing framework, configured in this workflow. This setup allows us to automatically run tests across multiple Python versions (3.10, 3.11, 3.12) on each push or pull request.

If you previously relied on tox for local testing across different Python versions, please note that this capability is no longer supported directly. Is this okay?

I need your input to decide whether to reintroduce tox or remove references to it from the documentation.

[Wim-De-Clercq]

For me all tox functionality exists elsewhere and doesn't provide something unique anymore which would not already be covered elsewhere. So I am in favour of dropping it.

• Running a test matrix of multiple setups and python versions: Github actions -- Sure you can't do this locally very easily. But I also don't even want to do this locally, why would I waste time running tests for several different versions. Just let CI do that and i'll dive deeper when necessary.

• Creating a python virtualenv of a specific python version: pyenv

[koenedaele]

Als alternatief voor de Travis badge lijkt er een Github workflow badge te zijn: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge

Ik heb de nieuwe build flow getest door de docs te volgen en dat werkt. Dus voor mij in orde, maar ik heb wel graag een nieuwe badge.

[koenedaele]

This button show the state of the tests (succes or failure), does something similar exist for Github actions?

[Wim-De-Clercq]

https://github.com/OnroerendErfgoed/atramhasis/actions/workflows/atramhasis_backend.yaml/badge.svg