[chirp_devel] Python 3 status

[Dan Smith]

> I have some practice dealing with Travis in the past even for automatic 
> releasing on tagging for a project (actually I'm learning Github Actions 
> for a project)

Thanks, I'm pretty familiar with travis myself and have used it in plenty of places. It's just the new pricing model that is the problem, not actually running the tests - those went fine after working through some of the weirdness of the chirp tests, which run with a split of site packages and venv because of lxml. But, the tests do a lot of work, about 300s per run, which will eat through the one-time gift of credits they gave people after the pricing change.

--Dan