> On 20 Dec 2022, at 6:54 am, Jonathan Vanasco <[email protected]> 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 > people still run 2.7/3.6 in production, so if a security fix is released for > those versions the fix can be applied to a commit with a functional test > environment. I find it much easier to just spend an extra 5-10 minutes > setting up that environment in advance "just in case" while I'm already > working on GitHub Actions, than spending 1-2 hours to suddenly re-familiarize > myself with the CI environment/setup and trying to jam legacy Python support > into it.
I’ll have a look at that and in general I’d agree but in this specific case since there is little movement in the project over time I don’t think it’s likely to be any updates for just security fixes - if there are security issues they’ve been there for a long time. There is a little bit of traction with some small changes in the last little while and since I use this library quite a bit I’d like to see if it can move forward a bit. Peter W. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/6CB8571F-E78D-44E9-BA1B-953136D9E4D3%40thirdfloor.com.au.
