Default python

T

takeda

There probably is a good reason for it, but I am drawing blank trying to understand it.

Basically, why there's an effort to set python3.13 as a default version (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292105) when there's already 3.15.0 released? Why not skip 3.13 and go to 3.14 or even 3.15 as since the effort takes time, by the time it is finished 3.15 will already have several releases. 3.13 has already stopped providing bugfixes, so we setting up default version that it is already in a maintenance mode.

I understand there were complications with 3.11 -> 3.12 which added a lot of delay to get 3.12, but why not catch up now and skip a version or two?
 
Ok that's a valid concern regarding 3.15 especially since it was released few days ago, but what about 3.14?

I think all packages would be updated by now to work with 3.14, the 3.14.0 was released a year ago so by now all maintained packages should be updated.
 
takeda said:
Ok that's a valid concern regarding 3.15 especially since it was released few days ago, but what about 3.14?

I think all packages would be updated by now to work with 3.14, the 3.14.0 was released a year ago so by now all maintained packages should be updated.
Click to expand...
I don't think they are. But I'm not on the Python team.
 
I found a site that seems to be tracking compatibility: http://pyreadiness.org/3.14/

Note that this is not accurate and only goes by the metadata specified in package, but I went through the top 120 and some on top 120-240 and the ones that are not marked as supported are either python independent or actually do have wheels even for version 3.15, the only exception I found was psexec which had wheel for 3.14.
 
You must log in or register to reply here.
Back
Top