github actions

[mamico]

see #90

• add tox
• add github actions (test + lint)
• make tests happy
• add coverage/coveralls
• cleanup (travis configs, badges, ...)

tox -e py27 works locally, I don't know if it is a good idea to work so that it can also work on github.

[fredvd]

@mamico Thanks for picking this up. the challenge with Python 2.7 support will be that github itself is deprecating or already has deprecated generic 2.7 support. Looking up.. has removed: actions/setup-python#672

So I'm not sure if we should still put the effor here in Python 2.7. Could Plone/meta help here as well?

[mauritsvanrees]

I would say: drop 2.7 support. Only support 3.8-3.11. Testing on 3.8 and 3.11 should be enough. Or start with only one Python.

We would be dropping support in a bugfix release, but that is because we chose to have the package version start with the Varnish version we support.

[mauritsvanrees]

I am not sure if coverage will work. I think I have seen problems years ago when I tried it on a buildout recipe, and lots of code was not picked up because coverage could not detect that this code was being run. Your mileage may vary.

For me, coverage is not needed. But sure, if it can be done, then it can be used to keep the coverage at a minimum level.

[mamico]

The tests are already running for py38 to py311, py27 run locally (if needed).

I will check for coverage.

[mamico]

@mauritsvanrees I confirm your experience. IMO the coverage does not detect code that is executed during system calls (ie system(bin/buildout)).

We can re-evaluate this in the future, for now I'll stop here.

[mauritsvanrees]

Thanks a lot!

[mauritsvanrees]

I have released 6.0.11 with this.
I needed to remove the towncrier config first, because it was not working. See commit 9fea808. You can restore it now if you want, and add a news/.gitkeep file, and some lines of explanation in CHANGES.rst.