hkage
commented
1 year ago I decided to remove the poetry setup because it is not intended to be used with Python 2.7 anymore (without further changes) and we are still using Python 2.7 on some servers, so that I cannot remove this compatibility. Therefore tox will be used for the test action and the local development has to be done by using simple virtualenvs.
The usage of f-strings recently broke the project's Python 2.7 compatibility which was added by intention. Unfortunately the Github tests didn't cover this incompatibility.
In addition to that the test action flow cannot handle the current poetry version / installer so that tests won't be executed properly (eg in this test run). The workflow has to be adjusted to the current poetry version or poetry has to be abolished in favor of simple requirement files and a Tox based testing setup.