Support Python 3.11 #728
Support Python 3.11 #728
Conversation
AntonOfTheWoods
force-pushed
the
py311
branch
from
ca6328d
to
79458a2
Compare
AntonOfTheWoods
force-pushed
the
py311
branch
2 times, most recently
from
6f6cfe9
to
1dca56a
Compare
|
Sorry @ayaka14732 , I push-forced and overwrote your change (and have since fixed it). We are going to have to wait for Github to publish 3.11 images unfortunately. Actually even Docker only just (less than 20 minutes ago) published their own images, even though the Hub page said they were available several hours ago... |
As the Anaconda folks can take months (or even years) to support new versions of python, also move to the conda-forge upstream repo, which is both much quicker and also the source of truth for the standard packages.
AntonOfTheWoods
force-pushed
the
py311
branch
from
1dca56a
to
09a23f3
Compare
AntonOfTheWoods
changed the title
|
@ayaka14732 , please have a look. I have removed the version bump to isolate this python-specific change. One thing is that the building gets done with anaconda ;-<. This means that we either have to wait for them to support python 3.11, or use conda-forge. It may take them months or even years to update - the company apparently doesn't care at all (ContinuumIO/anaconda-issues#13082). In this commit/PR, I have migrated to conda-forge as the source for the python executable. Upstream gets their versions from there, but haven't done so yet. |
|
Thanks @ayaka14732 , so we are now just waiting for an extra +1 to merge? If this is ok, I will also open a release PR with all the changelogs. |
No description provided.