Test Python 3.10 in tox workflow

[lukel97]

Mainly to match the Dockerfile image, but also so we can start testing other versions via a matrix

[boomanaiden154]

What's the purpose of this? If we're shipping things in Docker, I don't see a need to support more than a single python version. Supporting more than one adds complexity, especially around dependency management.

[lukel97]

AFAIK very few people use the Dockerfile today, I'm trying to get the ball rolling on that though in #60 and #55. I have no idea what versions of Python downstream instances are using so I didn't want to remove the coverage for the existing version.

[boomanaiden154]

AFAIK very few people use the Dockerfile today, I'm trying to get the ball rolling on that though in #60 and #55. I have no idea what versions of Python downstream instances are using so I didn't want to remove the coverage for the existing version.

Ack. Is there a list of downstream users somewhere that we could contact? It would be nice to know constraints around versioning.

[lukel97]

AFAIK very few people use the Dockerfile today, I'm trying to get the ball rolling on that though in #60 and #55. I have no idea what versions of Python downstream instances are using so I didn't want to remove the coverage for the existing version.

Ack. Is there a list of downstream users somewhere that we could contact? It would be nice to know constraints around versioning.

cc) @DavidSpickett

FWIW I agree that it would be good to constrain the number of python versions supported. I think this is probably part of a larger chunk of work of modernizing all the dependencies and moving away from setup.py

[DavidSpickett]

@antmox deals with our LNT server side.

I just care about the client, which is to run the test suite on the buildbots.