On Fri, 25 Oct 2019 at 16:16, Freddy Rietdijk <freddyrietd...@fridh.nl> wrote: > > I think it is more important to have CI that clearly shows the impact of dev > versions of the interpreter and core packages. Some of us in the Nixpkgs > community had this idea for Python core packages as well (and potentially > scientific computing packages, but that's out of scope here). This would need > funding though > https://discuss.python.org/t/funding-for-ci-for-integrating-development-versions-of-packages-and-interpreter-in-package-set/2540.
Agreed - I would consider having some sort of integration testing for core Python beta and various "important" packages to be a *far* better investment here. As you say, though, it's a big enough piece of work that it probably requires funding in some form. It's also worth noting that even with pre-release testing, there's still the non-trivial problem of getting any necessary fixes implemented and co-ordinated. That's a people-management issue, though, and IMO needs handling flexibly and in a way that's sympathetic to the fact that most of the projects involved are volunteer-based and resource starved. One of my biggest reservations about Victor's proposal is that it's basically removing flexibility and demanding extra testing, with little or no explanation of how we'd make that sustainable. Paul _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/Y2O255G4LRGZH656IUZ2R5GPO7NY2O4G/ Code of Conduct: http://python.org/psf/codeofconduct/
