It would be awesome if there was a way to have python update automatically update my eselect target for me. Obvious it shouldn't change the default interpreter but if 2.x updates we could update --python2 and 3.x could update --python3. Mostly this is an issue for those of us who update from a completely unattended script. With the new python-r1 eclasses becoming widely used I think it is pretty safe to do this by default, but I'd be happy with a use flag or a magic envvar or w/e the python team feels fit to provide.
Created attachment 365792 [details, diff] Add ESELECT_PYTHON_UPDATE_FORCE variable
Created attachment 365794 [details, diff] Cleanup eselect_python_update function The first patch is pretty safe. Let me know if that works for you. Did you want this on the stable ebuilds as well, or does ~arch suffice? Also, I would like to apply this second cleanup patch, but it is a little risky. If you could do me a favor and run it through a stage1 build when you have some time that would be most appreciated.
Optionally, we could use PYTHON_TARGETS to do extra safety check before switching. That is, switch only if user has appropriate target enabled.
(In reply to Michał Górny from comment #3) Any details on how you would implement that? Adding python_targets to IUSE on dev-lang/python is a bit awkward.
We no longer really want to use eselect-python automatically.
