-
Notifications
You must be signed in to change notification settings - Fork 272
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
Migrate build repo code from using Python 3.7 to 3.9 version #3351
Comments
The version 3.11 is currently feature adding version. Thanks. |
[TRIAGE] This is pre-req for #1563. |
Able to get the pip packages freeze version and didnt change behaviors on all the isort/flake8/mypy/pytest results.
Able to build/assemble artifacts for OS and OSD.
Able to run integTest on OS and OSD:
|
|
Windows Python3.9 Build and Assemble Runs now:
|
Also just fyi once we go to 3.9 all client release that uses this image |
We are starting the Python 3.9 Upgrade now, as Jenkins instance will be unstable from now on. An email to the team has been sent out last week. Thanks. |
Test deployment staging:
|
Verified all build and assemble on all platforms are running well. |
All docker actions are running ok with no issues. |
Will send to production and check gradle check. |
@peterzhuamazon We need to update developer guide too to use python 3.9 https://github.com/opensearch-project/opensearch-build/blob/main/DEVELOPER_GUIDE.md#python-37 |
Jenkins deploy success on production host and the migration deployment is complete. |
Adding meta task to update all 1-click release process: #3712 |
@peterzhuamazon Can we close this issue now? |
Yes @bbarani we have just completed all the changes now, thanks. |
Migrate build repo code from using Python 3.7 to 3.9 version.
Python3.7 support will ends on 2023/06/23.
https://endoflife.date/python
Note: 3.9 Ends in 2 years and 5 months (05 Oct 2025)
We need to migrate the code to Python 3.9 for the highest stability possible.
Acceptance Criteria:
cpython
with centos docker image.Thanks.
The text was updated successfully, but these errors were encountered: