From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Python 3.11 USE flags being flipped on
Date: Fri, 15 Dec 2023 01:38:53 +0200 [thread overview]
Message-ID: <ulg3me$13d9$1@ciao.gmane.io> (raw)
In-Reply-To: <34880f9a50de15dbd925603483ac1525@shitposting.expert>
On 15/12/2023 00:53, stefan11111@shitposting.expert wrote:
> I just tried to run today's emerge, when I saw that python 3.11 was
> being pulled in and packages had this USE flag flipped on.
Python 3.11 is the default right now (and has been for some months now.)
You should follow the python upgrade procedure (there should be a news
item for this, you can view those with "eselect news list".)
After the upgrade, it might be easier to block new python versions until
Gentoo switches the default version again later. This has been a
mainstay in my packacke.mask for ages now:
# Prevent a shitload of different python versions from being installed
<=dev-lang/python-3.10
>=dev-lang/python-3.12
(Obviously the versions are gonna differ over time.)
I don't set PYTHON_TARGETS nor PYTHON_SINGLE_TARGET. Currently, the
defaults are:
PYTHON_SINGLE_TARGET="python3_11"
PYTHON_TARGETS="python3_11"
When the default Python version changes, this is usually announced
through a portage news item and you'll get a notification about it when
you sync.
If you really want to stick to 3.10, you can try setting the above vars
for portage. You can do this in your package.use:
*/* PYTHON_TARGETS: -* python3_10
*/* PYTHON_SINGLE_TARGET: -* python3_10
However, 3.11 is the current default for a reason. Maybe some packages
really require it, and thus you will end up with both 3.10 and 3.11
installed. If you just want a single version installed, then it's a good
idea to not go against the current portage default.
next prev parent reply other threads:[~2023-12-14 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 22:53 [gentoo-user] Python 3.11 USE flags being flipped on stefan11111
2023-12-14 23:38 ` Nikos Chantziaras [this message]
2023-12-15 9:09 ` [gentoo-user] " stefan11111
2023-12-15 9:22 ` Arve Barsnes
2023-12-15 11:00 ` stefan11111
2023-12-25 0:11 ` James Massa
2023-12-16 9:47 ` Martin Vaeth
2023-12-27 1:00 ` stefan11111
2023-12-28 15:21 ` Martin Vaeth
2023-12-28 16:11 ` Arve Barsnes
2023-12-28 17:20 ` Martin Vaeth
2023-12-28 18:38 ` stefan11111
2023-12-28 18:50 ` Michael Orlitzky
2023-12-28 20:23 ` Martin Vaeth
2023-12-28 22:18 ` Martin Vaeth
2023-12-28 23:00 ` stefan11111
2023-12-29 1:07 ` Michael Orlitzky
2023-12-29 13:39 ` stefan11111
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ulg3me$13d9$1@ciao.gmane.io' \
--to=realnc@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox