On 6/5/24 4:27 AM, hitachi303 wrote: > Am 04.06.24 um 22:34 schrieb Eli Schwartz: >> - you read the news item, but decided to NOT defer the upgrade, and >> instead tried to mix both python 3.11 and python 3.12 together on your >> system > > > I do have one question because I get the vipe from you that mixing > python 3.11 and 3.12 would be a bad thing:
> the news item lists in the save upgrade section those lines: > */* PYTHON_TARGETS: -* python3_11 python3_12 > */* PYTHON_SINGLE_TARGET: -* python3_11 > > This is mixing python 3.11 and 3.12 on the same system. This should be > working as well, shouldn't it? Shouldn't portage be able to deal with > this, at least until python 3.11 gets deprecated? Why else would there > be the chance to define more than one python target? And both versions > of python are emerged in different slots. There might not be an > advantage and the disadvantage to carry around two versions of python > but shouldn't this work non the less? It's not a bad thing, and it should work fine. However the person who I was replying to, considers Gentoo to be broken if you have to set USE flags in order to perform a world update, and mixing multiple versions of python definitely requires you to set USE flags -- and if you only want to keep python 3.11 around for packages that don't support 3.12, rather than for all packages, then you would have to override PYTHON_TARGETS for a carefully selected list of packages rather than for */* So it is only mixing the two python versions that can ever *lead to having lots of package.use lines as a result of the update*. Which I think is fine, if people want that, but not everyone does, so delaying the update altogether might be preferable to those people. -- Eli Schwartz
OpenPGP_0x84818A6819AF4A9B.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
