On Sat, 2024-10-12 at 10:12 +0200, Michał Górny wrote: > This naturally means that only the specific version requested (e.g. via > targets) would be installed, and no cross-slot autoupgrades would > happen. Ideally, I'd like to start doing that with Python 3.14 whose > first alpha is expected next week. Depending on how they handle > freethreading, we'd end up having the first or both of: > > dev-lang/python3_14 > dev-lang/python3_14t > > (Alternatives: python-3_14, python-freethreading-3_14? Though I think > following PYTHON_TARGETS is cleaner here.) > > As a side notice, the existing versions would probably remain as-is > until removal, since there's really no gain in splitting them, given > we'd have to retain compatibility with existing depstrings. > > Comments?
Given all the opposition, I retract this. While this doesn't really change anything per se, I get that you can't stand the idea that someone wouldn't use slots for something where slot use doesn't really improve anything, and in fact makes users' lives worse. When someone complains that Portage suddenly installs Python 3.13 freethreading or Python 3.14 on their systems, it's on you. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
