Python Software Foundation wrote in April

We’re concerned that some of the current proposed policy language doesn’t make things clear enough for an ecosystem like Python’s. Under the current language, the PSF could potentially be financially liable for any product that includes Python code, while never having received any monetary gain from any of these products. The risk of huge potential costs would make it impossible in practice for us to continue to provide Python and PyPI to the European public.

which might be decided upon this year. CRA should have a grace period of 24 months.

Resolves YES if the PSF make Python unavailable for EU countries.

Resolves NO if the PSF makes no attempt to restrict Python for EU countries.

Whatever is done about PyPI does not matter for the resolution.