Packages show -python3_13

[jserink]

Hi All:

Most packages on my system refuse to build with python3_13 support.
Here is the top of my /etc/portage/package.use file:
jserinki7 /home/jserink # cat /etc/portage/package.use
*/* PYTHON_TARGETS: python3_11 python3_12 python3_13
*/* PYTHON_SINGLE_TARGET: -* python3_11


Here is what python's are installed:
jserinki7 /home/jserink # equery list python
* Searching for python ...
[I--] [??] dev-lang/python-2.7.18_p16-r1:2.7
[IP-] [ ] dev-lang/python-3.11.10_p1:3.11
[I-O] [ ~] dev-lang/python-3.12.7_p1:3.12
[I-O] [ ] dev-lang/python-3.13.0:3.13
[I-O] [ ] dev-lang/python-3.13.0-r100:3.13t

Here is an example:
jserinki7 /home/jserink/temp # emerge -pv dev-python/sphinx

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 10.43 s (backtrack: 0/20).

[ebuild R ] dev-python/sphinx-8.0.2::gentoo USE="latex -doc -test" PYTHON_TARGETS="python3_11 python3_12 (-pypy3) -python3_10 (-python3_13)" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB


Why do the use flags show -python3_13?
I have already run emerge -uDp --newuse world several times and it doesn't rebuild the dev-python packages with the python3_13 flag.

What am i doing wrong here?

Cheers,
john

[bstaletic]

USE flags python_targets_python3_13 and python_single_target_python3_13 are stable-masked, in profiles/base/use.stable.mask.
If you want packages built for/with python3.13, you'll have to either upgrade to testing or unmask the USE flags.

[jserink]

[logrusx]

[Maitreya]

That's the problem isn't it, 3.13 is marked as stable for some reason, while it really isn't worthy.
Nor is it used in packages yet, it doesn't built properly yet, so why it was unmasked is beyond me.
Maybe a small experiment from the devs?