On Mon, 8 Mar 2021 at 00:32, Steven Lembark wrote:
> * emerge: there are no ebuilds to satisfy
>
> > Q: Is there no way to have a consistent version of Python on
> >the system?
>
> Yes, make sure PYTHON_TARGETS and your chosen version of python match.
Q: How do I know which verson of python is suitable?
I never deal with the language... last I saw was some news that
turn off the
On Sun, 7 Mar 2021 23:47:26 +, Neil Bothwick wrote:
> > So, I go back and eselect 3.8.
> > I then try to perform some basic maintainence which fails for
> > lack of a python module I think is installed for python 3.8.
>
> If your system has been built entirely with
On Sun, 7 Mar 2021 18:32:26 -0500, Steven Lembark wrote:
> > 1) use eselect to set your default python to 3.8
> > 2) Add python_39 to PYTHON_TARGETS
> > 3) Explicitly call python38 in the shebang line of the affected
> > script.
>
> So, I go back and eselect 3.8.
> I then try to perform some
On Sun, 07 Mar 2021 19:30:21 +
Michael wrote:
> eselect python cleanup
> emerge --depclean -v -p
> emerge @preserved-rebuild -v -a
cleanup doesn't seem to change anything.
depcleand doesn't remove anything.
@preserved-rebuild failes due to lack of an already-installed
python library.
--
On Sun, 7 Mar 2021 22:04:39 +
Neil Bothwick wrote:
> But you have chosen a different default version of Python. That leaves
> you two choices:
>
> 1) use eselect to set your default python to 3.8
> 2) Add python_39 to PYTHON_TARGETS
> 3) Explicitly call python38 in the shebang line of the
On Sun, 7 Mar 2021 11:00:16 -0500, Steven Lembark wrote:
> I believe there isn't any PYTHON_TARGET-ish setting on the system:
>
> $ grep PYTHON_TARGET /etc/portage/make.conf
> /etc/portage/package.use/*
> /etc/portage/make.conf:#PYTHON_TARGETS="python3_7 python2_7"
>
t;>> Compiling source in
> >>> /tmp/portage/dev-python/pyyaml-5.4.1/work/pyyaml-5.4.1 ...
> ^Csandbox:stop caught signal 2 in pid 8217
> Sandboxed process killed by signal: Interrupt
> * The ebuild phase 'die_hooks' has been killed by signal 2.
>
>
yyaml-5.4.1 ...
^Csandbox:stop caught signal 2 in pid 8217
Sandboxed process killed by signal: Interrupt
* The ebuild phase 'die_hooks' has been killed by signal 2.
* Messages for package dev-python/pyyaml-5.4.1:
* Log file: /var/log/portage/dev-python:pyyaml-5.4.1:20210307-183833.log
> While eselect python is still available the OP can run:
>
> eselect python update
> eselect python cleanup
# eselect python update
Switching to python3.9
# eselect python cleanup
# eselect python list;
Available Python interpreters, in order of preference:
[1]
On Sunday, 7 March 2021 17:03:22 GMT Arve Barsnes wrote:
> On Sun, 7 Mar 2021 at 17:00, Steven Lembark wrote:
> > I believe there isn't any PYTHON_TARGET-ish setting on the system:
> > $ grep PYTHON_TARGET /etc/portage/make.conf
> > /etc/portage/package.use/*
> >
> >
On Sun, 7 Mar 2021 at 17:00, Steven Lembark wrote:
> I believe there isn't any PYTHON_TARGET-ish setting on the system:
>
> $ grep PYTHON_TARGET /etc/portage/make.conf /etc/portage/package.use/*
> /etc/portage/make.conf:#PYTHON_TARGETS="python3_7 python2_7"
>
On Sun, 7 Mar 2021 00:09:47 +0100
David Haller wrote:
> Hello,
>
> On Sat, 06 Mar 2021, Steven Lembark wrote:
> >Question then is why "python-exec2c" dispatched via a symlink from
> >"python3" would fail to see the installed copy of pyyaml (or how
> >should I check with modules are avalable via
13 matches
Mail list logo
