On Wed, Oct 23, 2013 at 9:13 AM, hasufell <hasuf...@gentoo.org> wrote: > Since I maintain blender I have come across quite a few frustrated > users already: https://bugs.gentoo.org/show_bug.cgi?id=488976#c7 > > I am not sure myself. On one hand we don't need python-updater anymore > and have very tight dependencies that ensure that all needed modules > are always available for the desired implementation. > > On the other hand it seems to give a lot of users trouble with > blockers, general configuration and mass-updates on things like > removing python:2.5. > > What are your opinions? Did it improve user experience? What could be > improved?
As one of the lead devs on the python team, here are my thoughts. I think we have made things more "correct". As a developer, it is much easier for me to tell when a package has incomplete or simply broken python dependencies. On the user side, I think we have traded occasional/random build failures due to mismatched python versions for some barely comprehensible portage dependency conflict messages. This is certainly not ideal, but I think it is always better to have portage fail during dependency resolution than at build time. The (non-)relationship between eselect python and PYTHON_TARGETS is something that would be nice to resolve, but I don't know how to do it. PYTHON_SINGLE_TARGET will probably cause problems if/when packages start supporting python3 only.
