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
Upgrade to Python 2.7.18 #27425
Comments
Dependencies: #27605 |
comment:3
As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9). |
This comment has been minimized.
This comment has been minimized.
comment:4
Python 2.7.17 release candidate 1 was released. From the
|
comment:5
Python 2.7.17 was released in October. Release announcement: One last release, Python 2.7.18, is planned for the end of December. Should we try to upgrade to 2.7.17 now? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:10
time to close this one as invalid ? |
comment:11
Right, Sage 9.1.1 won't happen, time to move on. |
If we ever decide to release Sage 9.1.1...
This ticket is to upgrade to Python 2.7.18,
so our last Python 2 version has the last Python 2.
**Tarball for Python 2.7.18: **
See: #29736 - Meta-ticket: Sage 9.1 maintenance
Depends on #27605
CC: @antonio-rojas @EmmanuelCharpentier @embray @kiwifb @timokau @jdemeyer @jhpalmieri @slel @tobihan
Component: packages: standard
Keywords: upgrade, python2
Issue created by migration from https://trac.sagemath.org/ticket/27425
The text was updated successfully, but these errors were encountered: