You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone!
Python 3.10.0 is already available via the setup-python action.
Unfortunately, it is not pre-installed on the images yet. New images with Python 3.10.0 will be deployed next week.
Reacted by D3r3k23, Sergey Vasilyev, Patrick Decat, dustin , Nikita Almakov, Sergey Tikhonov and Alexander Rodionov
Reacted by Sergey Vasilyev, Patrick Decat, Sergey Tikhonov, Sebastian Weigand, nikkie and Noritada Kobayashi
For anyone who comes across this, make sure to use quotes around 3.10, i.e. "3.10", as 3.10 as a float gets converted to 3.1
Reacted by jaypantone, Nobuhiro Ueda, Andrew McIntosh, Grzegorz Śliwiński, Morteza Milani, Ankur Sinha, Fabian Fröhlich, Unai Martinez-Corral, Max Kühn, Matt Hegarty and 56 more
Personally, I'd be tempted to at least consider making the float 3.1 map to "3.10" - the number of people using 3.1 should in theory be zero, and the number of users wondering why 3.10 produces a failure due to lack of "3.1" for most architectures is quite high, judging from twitter. After all, the fact that floats map to string versions is just a shortcut anyway - and a shortcut that has an unfortunate consequence for 3.10. By the time 3.20 rolls around, 3.2 should be even safer to map to 3.20, etc. (For those considering this a YAML bug, it has nothing to do with YAML - no language I know of maps 3.10 to anything but the float 3.1, and yaml does differentiate unambiguously between 3.10 (float) and "3.10" (string). It's just a shortcut that setup-python also accepts floats for version numbers. "3.1" would still access 3.1, if it's supported (I think it is on some platforms?)
It's kind of weird, so I probably would just continue let people correct their usage to all strings, but, just a thought.
Is 3.10 going to be installed by default at some point? It would be nice for it to be picked up by setup-nox, and I assume it would be faster to use, too.
Activity
hugovk commentedon Oct 5, 2021
For reference, it took 17 hours for Python 3.9 (#148) and 20 days for Python 3.8 (#30) :)
3.10 was released at 20:00 UTC yesterday, so 13:00 UTC today is your target!
MaksimZhukov commentedon Oct 5, 2021
Hello everyone!
Python 3.10.0 is already available via the setup-python action.
Unfortunately, it is not pre-installed on the images yet. New images with Python 3.10.0 will be deployed next week.
hugovk commentedon Oct 5, 2021
It wasn't two hours ago, but is now! (12 hours after release 👍 )
Thank you!
eddiebergman commentedon Oct 5, 2021
For anyone who comes across this, make sure to use quotes around
3.10, i.e."3.10", as3.10as a float gets converted to3.1hugovk commentedon Oct 5, 2021
For a longer explanation see: https://dev.to/hugovk/the-python-3-1-problem-85g
Special casing 3.10
Fix running tests with Python 3.10
Fix running tests with Python 3.10
Revert to Ubuntu 18.04
fix: quote "3.10" in ci
pbelskiy commentedon Oct 10, 2021
Thanks, but I when I will be available for GitHub actions? It's still problem with error:
hugovk commentedon Oct 10, 2021
@pbelskiy You need to use
actions/setup-python@v2notactions/setup-python@v1.henryiii commentedon Oct 12, 2021
Ah, this explains why setup-nox can't find 3.10, it activates all (pre-)installed versions.
henryiii commentedon Oct 12, 2021
Personally, I'd be tempted to at least consider making the float 3.1 map to "3.10" - the number of people using 3.1 should in theory be zero, and the number of users wondering why 3.10 produces a failure due to lack of "3.1" for most architectures is quite high, judging from twitter. After all, the fact that floats map to string versions is just a shortcut anyway - and a shortcut that has an unfortunate consequence for 3.10. By the time 3.20 rolls around, 3.2 should be even safer to map to 3.20, etc. (For those considering this a YAML bug, it has nothing to do with YAML - no language I know of maps 3.10 to anything but the float 3.1, and yaml does differentiate unambiguously between 3.10 (float) and "3.10" (string). It's just a shortcut that setup-python also accepts floats for version numbers. "3.1" would still access 3.1, if it's supported (I think it is on some platforms?)
It's kind of weird, so I probably would just continue let people correct their usage to all strings, but, just a thought.
Is 3.10 going to be installed by default at some point? It would be nice for it to be picked up by setup-nox, and I assume it would be faster to use, too.
11 remaining items
revert previous change; quote '3.10'
workflows: Python ver for 3.10 needs to be quoted
Fix Python 3.1 issue
Fix to install correct version 3.10 instead of 3.1:
Debug CI/CD pipeline: actions/setup-python#249 (comment)
Kneedle (#29)
Add Python 3.10 tests to GitHub Actions (#1292)
Kneedle (#29)
Docs improvement vol.1 (#32)
.github: pythonpackage: Fix py3.10 setup
.github: pythonpackage: Add py3.10 to matrix
.github: pythonpackage: Add py3.10 to matrix
Merge `v0.8.x` into `stable` (#1621)
Python 3.10 must be quoted per actions/setup-python#249
Quotated python 3.10, known issue: actions/setup-python#249