On Mon, Jul 10, 2017 at 01:04:10PM +0200, Pacho Ramos wrote: > Hello > > Looking to the list of packages still not supporting python 3.5: > https://qa-reports.gentoo.org/output/gpyutils/34-to-35.txt > > and considering that we should even start testing python 3.6, I think it would > be nice if we could make portage to warn when PYTHON_COMPAT value is not > updated. It's really frustrating to still see new ebuilds being added with > obsolete values for PYTHON_COMPAT and relying on a few people looking to > update > this. This is also causing huge delays to migrate to newer python versions > and I > think it's responsibility of the maintainer to ensure his/her package is > supported on newer versions or, at least, have a bug and ping upstream for the > cases they need further fixing. > > Of course, this wouldn't be a fatal check preventing you from committing a > package with outdated PYTHON_COMPAT, it would be a warning to remind you to > update it as soon as possible. > > Any issues on trying to go further into implementing this warning?
What about the situation where a package is not compatible with newer versions of python so does not need a PYTHON_COMPAT change? I don't think you can assume PYTHON_COMPAT is outdated for a package just because it doesn't have the latest versions of python listed. The only time you can know for sure that it is outdated is if it lists a version of python that no longer exists in the tree. William
signature.asc
Description: Digital signature
