-
-
Notifications
You must be signed in to change notification settings - Fork 510
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 to 3.9.1, pip to 20.3.3 #30589
Comments
Dependencies: #30184 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch: u/mkoeppe/upgrade-python-3.9 |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Changed dependencies from #30184 to none |
This comment has been minimized.
This comment has been minimized.
comment:13
3.9.1 is out https://www.python.org/downloads/release/python-391/ "3.9.1 is the first version of Python to support macOS 11 Big Sur. With Xcode 11 and later it is now possible to build “Universal 2” binaries which work on Apple Silicon. We are providing such an installer as the macos11.0 variant. This installer can be deployed back to older versions, tested down to OS X 10.9. As we are waiting for an updated version of pip, please consider the macos11.0 installer experimental." |
comment:14
Not sure which updated version of pip they are referring to. 20.3 (2020-11-30) lists "Add support for MacOS Big Sur compatibility tags. (#9138)" https://pip.pypa.io/en/stable/news/#id15 No new news items regarding Big Sur in 20.3.3 (2020-12-15) |
This comment has been minimized.
This comment has been minimized.
comment:25
We can also try to throw in an upgrade of |
comment:27
Replying to @jhpalmieri:
But doesn't the python3 from XCode work? |
comment:28
Right now homebrew's python3 is shadowing Xcode's, so I don't know. I would rather not uninstall homebrew's since it is used by other homebrew packages that I want to keep. I have bigger issues right now: I can make almost no progress building Sage with 9.3.beta4. For example, with #31050 merged with beta4,
Is my command-line tools installation broken? It is certainly true that the named In contrast, with just #31050 (which was based on beta3), I see the following in the
(same wrong path given to Separately, on a machine running Catalina, I'm having problems with |
comment:29
In a (working) Homebrew installation on Catalina, I don't have these This can be seen in config.log |
comment:30
(For |
comment:31
Well, this is probably not the right thing to do in the long term, but I created a symlink connecting
but the other problems seem to be solved. |
comment:32
Replying to @jhpalmieri:
scipy probably needs an update, and/or a hack: |
comment:33
I'm not clever enough to figure out how to hack Edit: the error with
This is with this ticket and an updated |
comment:34
I guess we should move my derailment of the discussion to #30651. |
comment:35
Does someone have time to review this ticket? The tests have already run successfully. Note that an update to latest 3.8.x is not a good alternative: https://www.python.org/downloads/release/python-387/ Python 3.8.7 is not yet fully supported on macOS 11 Big Sur. It will install on macOS 11 Big Sur and will run on Apple Silicon Macs using Rosetta 2 translation. However, a few features do not work correctly, most noticeably those involving searching for system libraries (vs user libraries) such as ctypes.util.find_library() and in Distutils. This limitation affects both Apple Silicon and Intel processors. We are looking into improving the situation for Python 3.8.8. |
comment:38
On macOS 10.14.6 with lots of Homebrew packages, $ git trac checkout 30589
$ source .homebrew-build-env
$ ./bootstrap -q
$ ./configure --without-system-python3 --enable-download-from-upstream-url -q
$ make -s V=0 resulting in a build of Sage 9.3.beta4 based on Python 3.9.1. But something that worked for another Sage install currently at 9.3.beta5: $ V=0 sage -i pynormaliz failed here while attempting to build e-antic. |
comment:39
On OS X Big Sur + various homebrew packages, if I use
then Sage builds (if I also incorporate various other changes from #30651), but I get doctest failures of the form
We could (a) not worry about these for now, (b) filter out these warnings, (c) tinker with |
comment:40
These linker warnings are annoying and I think we should filter them out for the doctests. I think it should be a separate ticket. I think I have seen them on other platforms too. |
comment:41
This is now #31204 |
comment:42
Replying to @slel:
Is this on homebrew too? |
comment:43
In any case, let's worry about optional packages like e-antic later. Let's get this in please. |
comment:44
Sure, let's proceed. |
Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/426748847 to John Palmieri, Samuel Lelièvre |
Changed branch from u/mkoeppe/upgrade-python-3.9 to |
This contains the upgrade to Python 3.9.1
To test, use
Depends on #31050
CC: @slel @jhpalmieri @fchapoton @dimpase @vbraun @kiwifb
Component: packages: standard
Author: Matthias Koeppe
Branch/Commit:
41d7e7a
Reviewer: John Palmieri, Samuel Lelièvre
Issue created by migration from https://trac.sagemath.org/ticket/30589
The text was updated successfully, but these errors were encountered: