> On 20 Dec 2022, at 7:38 am, Bert JW Regeer wrote:
>
> If you want to put together a PR that moves to Github actions (feel free to
> steal from any of our other repos, and in fact I encourage it so that it is
> easier to maintain for us moving forward see; pyramid/waitress/webob/others).
>
> On 20 Dec 2022, at 6:54 am, Jonathan Vanasco wrote:
>
> But as a personal preference, while I don't use this library myself, whenever
> I move a project onto GitHub actions I initially maintain support for 2.7 and
> 3.6 then drop those versions in a second commit. The reason is that many
Most of the projects that Michael and I maintain we use the current supported
version of Python and up. We drop older versions when we get around to touching
the repo because maintaining older versions of Python and testing/validating is
a pain.
If you want to put together a PR that moves to
I can't speak for the maintainers, but the Pylons Projects have been
standardizing onto Github Actions so there is appeal. IIRC, support for
projects has also been targeting 3.7+.
But as a personal preference, while I don't use this library myself,
whenever I move a project onto GitHub
