ottembomb Posted October 6, 2017 Report Share Posted October 6, 2017 Good morning after a bit of a rocky transition to the new kit setup, I've noticed that eselect set python X doesn't seem to be working: mediaserver ~ # eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 [3] python2.7 (fallback) mediaserver ~ # eselect python set 1 mediaserver ~ # eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 [3] python2.7 (fallback) No asterisk after python3.4 However eselect kernel seems to be working appropriately: mediaserver ~ # eselect kernel list Available kernel symlink targets: [1] linux-4.9.4-gentoo [2] linux-4.9.7-gentoo [3] linux-4.10.1-gentoo [4] linux-4.10.4-gentoo [5] linux-4.10.13-gentoo [6] linux-4.11.3-gentoo [7] linux-4.12.1-gentoo [8] linux-4.12.4-gentoo [9] linux-4.13.3-gentoo * [10] linux-4.13.4-gentoo [11] linux-4.13.5-gentoo Is this normal? THanks in advance, Link to comment Share on other sites More sharing options...
0 Sandro Posted October 6, 2017 Report Share Posted October 6, 2017 It is all right; The first in the list will be the "default" then the others. for example: ci74771ht ~ # eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 [3] python2.7 Then 3.4 will be the default. Now i make: ci74771ht ~ # eselect python list Available Python interpreters, in order of preference: [1] python3.5 [2] python3.4 [3] python2.7 Now the first in list is the python3.5 (that i've unmasked for my necessity). If I want python-3.4 at first # eselect python set 2 # eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 [3] python2.7 if you want to see with your eyes, you can install # emerge python-updater Then # python-updater In Funtoo python-updater is deprecated cause the work will be made by Portage itself .... _'_ Link to comment Share on other sites More sharing options...
0 rsa4046 Posted October 6, 2017 Report Share Posted October 6, 2017 Hi ottembomb, what about inserting the --python3 action to list or set. # eselect python list Available Python interpreters, in order of preference: [1] python2.7 [2] python3.4 ? ? E.g., # eselect python list --python3 Available Python 3 interpreters, in order of preference: [1] python3.4 Link to comment Share on other sites More sharing options...
0 Sandro Posted October 6, 2017 Report Share Posted October 6, 2017 Ugh isa4046 : excuse me :| we are wrote at the same time .... excuse me i can see now your answer :| Link to comment Share on other sites More sharing options...
0 dhudson Posted October 6, 2017 Report Share Posted October 6, 2017 I saw in a news item a while ago that eselect python would go away.. No idea if it did butl I think ego is taking care of it since change to kits. an example editing of /etc/ego.confsetting python-kit = 3.6-primerunning epro update. info is from https://bugs.funtoo.org/projects/FL/issues/FL-4270?filter=allissues I know that bug was concerning lv2 but shows how to correctly switch python versions with kits. IMO. Please correct me if i'm wrong! dave Link to comment Share on other sites More sharing options...
0 ottembomb Posted October 7, 2017 Author Report Share Posted October 7, 2017 Thanks to you all for the help. Link to comment Share on other sites More sharing options...
0 Sandro Posted October 7, 2017 Report Share Posted October 7, 2017 ci74771ht ~ # cat /etc/ego.conf # This is the ego.conf file [kits] # You can set your default kits here. Unset kits will use the Funtoo default prime/master # branch by default. # python-kit = 3.6-prime # core-hw-kit = master # core-kit = master # desktop-kit = master # dev-kit = master # editors-kit = master # games-kit = master # gnome-kit = master # java-kit = master # kde-kit = master # media-kit = master # net-kit = master # nokit = master # perl-kit =master # php-kit = master # python-kit = master # science-kit = master # security-kit = master # text-kit = master # xorg-kit = master I've added all kits in /etc/ego.conf but commented. If you want to switch to master ... you can uncomment one or more raw in this files to use "master branch". But is only a idea of mine ; in the future there will be commands to control kits with new instructions. At this moment i work with this "method" (that is very simply). Bye :) Link to comment Share on other sites More sharing options...
Question
ottembomb
Good morning
after a bit of a rocky transition to the new kit setup, I've noticed that eselect set python X doesn't seem to be working:
No asterisk after python3.4
However eselect kernel seems to be working appropriately:
Is this normal?
THanks in advance,
Link to comment
Share on other sites
6 answers to this question
Recommended Posts