Hello friends, On Sunday, October 29, 2017, Alan McKinnon <alan.mckin...@gmail.com> wrote: > On 29/10/2017 11:11, Peter Humphrey wrote: >> On Sun, 29 Oct 2017 19:31:46 +1100 >> Adam Carter <adamcart...@gmail.com> wrote: >> >>>> On my amd64 arch machine I; >>>> emerged python 3.5 >>>> eselected python 3.5 >>>> edited make.conf to set PYTHON_TARGETS to "python2_7 python3_5" >>>> running emerge -pv --depclean =python-3.4.5 to see what needs to be >>>> rebuilt Then tryed to rebuild those packages to allow removal of 3.4, >>>> however, it looks like that I would then have to change >>>> PYTHON_SINGLE_TARGET to 3.5 too, and some other packages still require >>>> it to be set to 2.7, so i've bailed out of trying to get rid of 3.4 on >>>> that box. I'll leave PYTHON_TARGETS at "python2_7 python3_5" unless I >>>> find something that also needs 3.4 in there. >>>> >>>> Failure came fast, example; >>> The following REQUIRED_USE flag constraints are unsatisfied: >>> python? ( at-most-one-of ( python_targets_python3_4 >>> python_targets_python3_5 python_targets_python3_6 ) >>> >>> So ive unset PYTHON_TARGETS and PYTHON_SINGLE_TARGET again. >> >> Do you actually need any python entries in make.conf? I'm running happily >> here without any. I just let the profile and ebuilds sort out what they >> need. >> > > > For the most part, and for the regular user, that is generally fine. The > devs and profile maintainers take care of all the fiddly bits and ensure > that the settings are correct across the tree when they update the > profile to use the next Pythn version > > For some users (aka the typical Gentoo'er) that doesn't really cut it. > Maybe the user wants to fiddle with python-3.5 before the profile is > ready for it. > > Maybe the user wants to use some nifty new package or take advantage of > new features in python-3.5. This is the thing R0b0t1 was referring to. > In that case, the user must do for himself what the profile maintainers > do for you. That user also gets to keep all the shiny broken bits whilst > figuring out what to set for what >
I've mentioned this on the forum, but unless a user is interested in specifically testing Python's interaction with system packages it is probably best to merge new versions explicitly. There will be lots of shiny pieces indeed. Cheers, R0b0t1.