On 05. 07. 22 16:02, Richard W.M. Jones wrote:
On Tue, Jul 05, 2022 at 03:46:47PM +0200, Miro Hrončok wrote:
> On 05. 07. 22 15:05, Richard W.M. Jones wrote:
>> On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote:
>>> forwarding this message to Fedora.
>>> Will know more by the end of this week -- we might need to consider
>>> reverting back to Python 3.10 if we don't want to ship Fedora 37 GA
>>> with a beta version of Python:(
>> Is there a reason why shipping a beta version of Python would be bad?
>> I've been using it on my main development machine for a few weeks and
>> for the (fairly limited) Python stuff I do it seems to be fine.
>> It'd be a problem if it was causing bugs.
> I suppose it could amplify the "Fedora is the bleeding edge" message.
Which is good :)
So one issue is if Python is intending to add new features between now
and the final release of 3.11, and then other software might (in
future) check for the presence of some new feature by using a version
number test. Since our beta Python would look sufficiently like 3.11,
it might report as having the new feature.
That is not intended. In fact, it is forbidden by Python policies. Python 3.11
is feature complete, features can only be reverted at this point.
Is it possible to update Python to 3.11 after Fedora 37 GA is
Maybe. We can do it if it is ABI compatible with the beta we shipped at GA.
Upstream only guarantees ABI compatibility at RC :/