-
-
Notifications
You must be signed in to change notification settings - Fork 491
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: Python 3.8.5 #27754
Comments
comment:1
If people want to start testing, Python 3.8.0a3 is out: |
comment:2
I think it's a bit early for testing. I'd rather wait for the first beta, which is supposed to be released later this month. |
comment:3
Python 3.8.0b1 is out: |
comment:4
Note: this requires a Cython upgrade. |
comment:5
Cython upgrade needs review at #27886. |
Changed keywords from none to days101 |
Dependencies: #28012 |
comment:7
I'll have a look at this today. |
This comment has been minimized.
This comment has been minimized.
Author: Jeroen Demeyer |
Branch: u/jdemeyer/upgrade__python_3_8_x |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
Changed dependencies from #27886 to none |
comment:12
Actually, thanks to two patches which are likely going to be accepted upstream, it no longer depends on the Cython upgrade. |
Upstream: Reported upstream. Developers acknowledge bug. |
comment:14
There is a mysterious build failure of matplotlib:
But when running Python normally,
I have no clue how this could happen. |
comment:15
I tried this with OS X and ran into a problem with Pillow:
Here is the problem code from Pillow's setup.py:
Python 3.7.3 does this:
The new Python does this:
|
comment:16
I see the same problem with matplotlib. For laughs, I put a If I run
|
comment:17
Replying to @jhpalmieri:
That makes no sense. Somebody is fooling with us... Could you try also Just in case, I checked that the problem unfortunately persists after And a Google search for this error doesn't find anything. |
comment:18
I'm guessing the problem is coming from
|
comment:19
My question is why it worked with Python 3.7.3 but not 3.8.0. |
comment:209
Okay, this works for me on OS X with the system Python and Sage's Python 3.8, and the same on a virtual Debian 32-bit machine. |
comment:210
Great! |
comment:211
Merge conflict |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
comment:218
FWIW, worked for MeToo(TM) : Rebuilding |
comment:219
it even works on Rasberry Pi 4 (armv7l). |
Changed branch from public/python3.8 to |
comment:221
Wonderful to have this in Sage 9.2. Next episode:
(Python 3.9.rc2 is expected on 2020-09-14 |
Changed commit from |
This is to upgrade to Python 3.8.x.
Tarball: see checksums.ini
Previous and next Python upgrades:
See also:
Depends on #28197
Depends on #29042
Depends on #29861
Depends on #30162
Depends on #30225
Depends on #30127
Depends on #30144
Depends on #30345
Depends on #30365
Depends on #30140
Depends on #30351
Upstream: Reported upstream. Developers acknowledge bug.
CC: @fchapoton @embray @kiwifb @jdemeyer @mkoeppe @slel @timokau @isuruf @kliem @tscrim @heluani @sheerluck
Component: packages: standard
Keywords: days101
Author: Jeroen Demeyer, John Palmieri, Matthias Koeppe, Antonio Rojas
Branch:
f1cda12
Reviewer: Matthias Koeppe, François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/27754
The text was updated successfully, but these errors were encountered: