@Makyen Same reason as what you mentioned in your comment at the answer in question. I checked the users profile and found this same answer. Well, now they're all gone.
@Makyen i commented on #3893 I think that it's a good idea to test supported releases, but 3.6.11, 3.7.8, and 3.8.3 specifically if we can - currently latest Python of those three variants/minor revs.
i do this with all my PyPI modules and enforce Earliest Supported -> Latest testing for my CIs.
@πάνταῥεῖ Your initial feedback appeared to come prior to the second answer being posted. The first answer was actually an answer to the question, so would have been FP, unless be can find some indication of undisclosed affiliation. After the user posted the second answer, it was more likely they were here to promote, rather than someone just posting a low quality answer. Basically, we need to give people a bit more benefit of doubt. I'm not saying go overboard doing so, just a little bit more.
@ThomasWard That sounds reasonable to me. I'll put it as a task to set up more versions for CI testing. You are, of course, welcome to do so, given that you're already done it elsewhere. :) Given that we're working on this, I wonder if we should remove 3.5 testing at this time. Its EOL is 2020-09-13, so this is a couple/few months early, but as long as we're already working on changes...
