-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Python 3.10 (release) #4226
Comments
Hello @nolar! |
For reference, it took 22 days for Python 3.9 (#1740) on Azure Pipelines and 24 days for Python 3.8 (https://web.archive.org/web/20201012044438/https://github.com/microsoft/azure-pipelines-image-generation/issues/1317) :) |
@nolar @hugovk Python 3.10 is already available through https://github.com/actions/setup-python and will be pre-cached on the next week's images. |
Thank you! Confirmed now available for GitHub Actions: actions/setup-python#249 (comment) Does Azure Pipelines need to wait for the pre-cached images next week?
|
Please could we re-open this to track Azure Pipelines? Or shall I open a new issue (here or elsewhere)? |
Sorry. Reopened. |
@hugovk correct, AzDO task can't download the version on demand so we have to wait until the new images are available |
Just tried adding 3.10 to our repo and it failes:
cause the pipeline to think it must use '3.1' i.e. removes the trailing zero. The failing PR is here: datatrails/datatrails-python#64 |
Short version: put quotes around the versions, so it interprets "3.10" as a string and not 3.10 as a float => 3.1: python-version: ["3.6", "3.7", "3.8", "3.9", "3.10"] Longer version: https://dev.to/hugovk/the-python-3-1-problem-85g |
ah thanx - alt=ready saw this when inspacting the commit here... |
Small update — macOS and windows images with pre-cached python 3.10 will be deployed this week, ubuntu — next week. |
@miketimofeev I've run into two problems so far
|
@charris for the first one — yes, it's deliberate as we didn't add 32-bit versions of Python to windows-2022 and received no complaints so far, so we decided not to add 32-bit versions of python 3.10 to all the other windows versions. If it's an issue for you we can consider adding them. |
@miketimofeev No problem with no 32 bit 3.10 on windows, we would prefer to drop it ourselves. As to the missing |
@miketimofeev The problem looks to be a change in Python 3.10 distutils. |
Mac problem is due to the multibuild software we use only supporting universal2 wheels. |
@charris we have a feature request to support universal2 builds and a PR as well but didn't have a chance to validate it yet actions/python-versions#114 |
@miketimofeev - I think it is a problem, dropping the 32-bit Windows environment - based on some recent comments by @zooba - see scipy/scipy#14316 (comment) . In particular @zooba suggested the need to keep supporting 32-bit in order to support ARM64 users on Windows. |
@matthew-brett for GitHub actions the recommended way is to use setup-python action, which will install the version on the flight. For AzDO there is no such way, so we will monitor for the requests. |
Quotes have been added around the version numbers to mitigate the Python 3.1 problem. actions/runner-images#4226 (comment)
@nolar Python 3.10 should be available everywhere. |
Thank you! I count that as 17 days since Python 3.10, an improvement over last year's 22 days since 3.9 and the year before's 24 days since 3.8! 🎈👏 |
Tool name
Python
Tool license
PSF
Add or update?
Desired version
3.10 (released yesterday)
Approximate size
No response
Brief description of tool
No response
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Virtual environments affected
Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: