Ühel kenal päeval, E, 10.04.2017 kell 14:44, kirjutas William L. Thomson Jr.: > Again go modify a few hundred python packages to remove say 3.4. I > think about 10-20 ebuilds in. You will be scripting and looking for > another way....
No, for that you simple remove python3_4 from _PYTHON_ALL_IMPLS in python-utils-r1.eclass and call it a day. Some other day you might make a mass commit to remove 3_4 from PYTHON_COMPAT of all in-tree ebuilds, but that's just janitorial and no other effect. The current implementation makes perfect sense to me, and follows one of the zens of python: Explicit is better than implicit. Declare explicitly what version is supported, don't implicitly do so and merely hope there are no issues. If some lower level module doesn't work with new python and your higher level module wants to use the new python, repoman will catch it for you due to it having been explicit via PYTHON_USE_DEP. There is no difference with reverse approach if one would mass commit the new COMPAT into all ebuilds upon the introduction of a new python slot, but this is not done, because things would break. Mart
