Re: [gentoo-user] python mess - random winge!
On Tue, 5 Jul 2022 11:17:27 +0200, Petr Vaněk wrote: > > It is already CONFIG_PROTECTed, I had to approve the changes in the > > usual way before they went ahead. What I find slightly odd is that > > this file is also managed by eselect-python, but that is not > > installed by default. I would have expected it to be part of @system. > > > > This change is described in > https://www.gentoo.org/support/news-items/2021-01-30-python-preference-to-follow-python-targets.html Worth reading, I missed that one, thanks. -- Neil Bothwick "Do you reply to our surveys.?" [X]Never [ ]Always [ ]Sometimes pgpDCoe_dvja1.pgp Description: OpenPGP digital signature
Re: [gentoo-user] python mess - random winge!
On Tue, Jul 05, 2022 at 08:56:11AM +0100, Neil Bothwick wrote: > On Tue, 5 Jul 2022 15:31:38 +0800, William Kenworthy wrote: > > > I did read the news item and set the systems as above with multiple > > python targets - there is no mention of python-exec and its role in > > which python version is in use for packages that just call "python". > > Perhaps I should have been clearer - what I see is with multiple python > > targets present the python ebuild automatically selects the latest > > version that is stable via python-exec - ok, some would want that. But > > what it should do is respect the users choice of running version and not > > automaticly overide it without asking. It looks like python-exec is the > > controlling factor so I'll try CONFIG_PROTECTon that file and manually > > manage it via ansible. > > It is already CONFIG_PROTECTed, I had to approve the changes in the usual > way before they went ahead. What I find slightly odd is that this file is > also managed by eselect-python, but that is not installed by default. I > would have expected it to be part of @system. This change is described in https://www.gentoo.org/support/news-items/2021-01-30-python-preference-to-follow-python-targets.html Petr
Re: [gentoo-user] python mess - random winge!
On Tue, 5 Jul 2022 15:31:38 +0800, William Kenworthy wrote: > I did read the news item and set the systems as above with multiple > python targets - there is no mention of python-exec and its role in > which python version is in use for packages that just call "python". > Perhaps I should have been clearer - what I see is with multiple python > targets present the python ebuild automatically selects the latest > version that is stable via python-exec - ok, some would want that. But > what it should do is respect the users choice of running version and not > automaticly overide it without asking. It looks like python-exec is the > controlling factor so I'll try CONFIG_PROTECTon that file and manually > manage it via ansible. It is already CONFIG_PROTECTed, I had to approve the changes in the usual way before they went ahead. What I find slightly odd is that this file is also managed by eselect-python, but that is not installed by default. I would have expected it to be part of @system. -- Neil Bothwick Quick!! Act as if nothing has happened! pgpnLMVX4Bro0.pgp Description: OpenPGP digital signature
Re: [gentoo-user] python mess - random winge!
On 5/7/22 14:24, w...@op.pl wrote: > Dnia 2022-07-05, o godz. 13:04:07 > William Kenworthy napisał(a): > >> I synced portage a couple of days now and now my systems are >> rebuilding python modules for 3.10 without any input from me (prior >> to this 3.10 was on the system but wasn't picked up by applications.) >> This is breaking non portage apps like homeassistant which are still >> not fully 3.10 safe - ok that's sort of expected and in this case >> will be fixed, but I cant find anything definitive on the task of "I >> want to control which python is used" and when to update. >> >> I eventually found that changing the order in python-exec.conf helped >> on the homeassistant system. There is a LOT of out of date >> documentation out there, particularly with eselect being used but is >> actually not used with python anymore (why? - from a user point of >> view having consistent access to configuration is a no brainer!) - so >> how can one get python to behave reliably and override its automatic >> get things wrong installation system? Is manually editing >> python-exec.conf the way (which seems to get overwritten - shouldn't >> that be a protected config file then?) >> >> BillK >> >> >> >> > Hello! > > In "eselect news" info about python update there is a paragraph about > blocking the upgrade. It just means adding: > > */* PYTHON_TARGETS: -* python3_9 > */* PYTHON_SINGLE_TARGET: -* python3_9 > > to /etc/portage/make.conf or /etc/portage/package.use or > /etc/portage/package.use/zz-somename - whichever suites you best. > > You can also change these settings just for some packages, by adding: > > cat/pkg PYTHON_TARGETS: -* python3_9 PYTHON_SINGLE_TARGET: -* python3_9 > > to one of aforementioned files. > > Hope that helps! I did read the news item and set the systems as above with multiple python targets - there is no mention of python-exec and its role in which python version is in use for packages that just call "python". Perhaps I should have been clearer - what I see is with multiple python targets present the python ebuild automatically selects the latest version that is stable via python-exec - ok, some would want that. But what it should do is respect the users choice of running version and not automaticly overide it without asking. It looks like python-exec is the controlling factor so I'll try CONFIG_PROTECTon that file and manually manage it via ansible. BillK
Re: [gentoo-user] python mess - random winge!
Dnia 2022-07-05, o godz. 13:04:07 William Kenworthy napisał(a): > I synced portage a couple of days now and now my systems are > rebuilding python modules for 3.10 without any input from me (prior > to this 3.10 was on the system but wasn't picked up by applications.) > This is breaking non portage apps like homeassistant which are still > not fully 3.10 safe - ok that's sort of expected and in this case > will be fixed, but I cant find anything definitive on the task of "I > want to control which python is used" and when to update. > > I eventually found that changing the order in python-exec.conf helped > on the homeassistant system. There is a LOT of out of date > documentation out there, particularly with eselect being used but is > actually not used with python anymore (why? - from a user point of > view having consistent access to configuration is a no brainer!) - so > how can one get python to behave reliably and override its automatic > get things wrong installation system? Is manually editing > python-exec.conf the way (which seems to get overwritten - shouldn't > that be a protected config file then?) > > BillK > > > > Hello! In "eselect news" info about python update there is a paragraph about blocking the upgrade. It just means adding: */* PYTHON_TARGETS: -* python3_9 */* PYTHON_SINGLE_TARGET: -* python3_9 to /etc/portage/make.conf or /etc/portage/package.use or /etc/portage/package.use/zz-somename - whichever suites you best. You can also change these settings just for some packages, by adding: cat/pkg PYTHON_TARGETS: -* python3_9 PYTHON_SINGLE_TARGET: -* python3_9 to one of aforementioned files. Hope that helps! -- xWK pgp5vGReLrLfC.pgp Description: Podpis cyfrowy OpenPGP
Re: [gentoo-user] python mess - random winge!
On 7/4/22 22:04, William Kenworthy wrote: > I synced portage a couple of days now and now my systems are rebuilding > python modules for 3.10 without any input from me (prior to this 3.10 > was on the system but wasn't picked up by applications.) This is > breaking non portage apps like homeassistant which are still not fully > 3.10 safe - ok that's sort of expected and in this case will be fixed, > but I cant find anything definitive on the task of "I want to control > which python is used" and when to update. As Nikos mentioned in another reply, you should pay attention to the eselect news items as python upgrades are usually announced weeks in advance. > > I eventually found that changing the order in python-exec.conf helped on > the homeassistant system. > There is a LOT of out of date documentation > out there, particularly with eselect being used but is actually not used > with python anymore (why? - from a user point of view having consistent > access to configuration is a no brainer!) I don't see any deprecation notice on https://packages.gentoo.org/packages/app-eselect/eselect-python, but someone could correct me. > - so how can one get python to > behave reliably and override its automatic get things wrong installation > system? Is manually editing python-exec.conf the way (which seems to > get overwritten - shouldn't that be a protected config file then?) The python package supports installing multiple versions to different slots. The easiest way I've found to run python software that depends on a specific version, without mucking around with global python settings, is to install the relevant version (e.g. emerge python:3.8) and then use venv to run that software in a virtual environment (python3.8 -m venv .env; .env/bin/python something.py). > > BillK
[gentoo-user] python mess - random winge!
I synced portage a couple of days now and now my systems are rebuilding python modules for 3.10 without any input from me (prior to this 3.10 was on the system but wasn't picked up by applications.) This is breaking non portage apps like homeassistant which are still not fully 3.10 safe - ok that's sort of expected and in this case will be fixed, but I cant find anything definitive on the task of "I want to control which python is used" and when to update. I eventually found that changing the order in python-exec.conf helped on the homeassistant system. There is a LOT of out of date documentation out there, particularly with eselect being used but is actually not used with python anymore (why? - from a user point of view having consistent access to configuration is a no brainer!) - so how can one get python to behave reliably and override its automatic get things wrong installation system? Is manually editing python-exec.conf the way (which seems to get overwritten - shouldn't that be a protected config file then?) BillK