El lun, 10-07-2017 a las 13:12 +0200, Kristian Fiskerstrand escribió: > On 07/10/2017 01:04 PM, Pacho Ramos wrote: > > Any issues on trying to go further into implementing this warning? > > Not an issue per se, but it should be pointed out that python 3.5 only > has a testing visibility, so this at the very least requires maintainers > to potentially have a separate testing chroot/VM to test when adding the > compat. >
Yes, but it's similar as the cases when we need to fix our packages to work with a newer library they depend on. In this case it would be even easier as we can have multiple python versions and switch to the newer one for testing while going back to the stable one (if preferred) later.
