-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Update pip to 9.0.1 #23615
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
Branch: u/mderickx/23615 |
New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
This looks very scary: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
Yeah, I shouldn't have written that. Changed it into |
comment:8
Builds fine and passes tests for me on OS X. Note that on this machine, the
and |
comment:9
Replying to @jhpalmieri:
Build from scratch or just a regular upgrade? I'm going to test a build from scratch on Linux. |
comment:10
Replying to @jdemeyer:
Build from scratch. |
Reviewer: Jeroen Demeyer |
Changed branch from u/mderickx/23615 to |
comment:13
It seems that this breaks something with python3... :(
|
Changed commit from |
comment:14
oh, wait a moment. I did not rebuild.. |
comment:15
Apparently, this really did break the python3 build. I am not amused. |
comment:16
Hi Chapoton, I would find it weird if this really did break the python3 build. The error message you posted is one that one would get if the installed pip is not actually 9.0.1: For example on my machine with sage before this was merged
and after it is merged
Could you give me the output of |
comment:17
A quick solution would be:
This avoids doing:
|
comment:18
so maybe this is a matter of pip versus pip3 ? EDIT: in a sage shell, pip3 says version 9.0.1 too. |
comment:19
Weird, then the only possibility is that sage is picking up some pip from outside its installation. Could you add the lines
before the lines:
in Alternatively could you describe how to reproduce this error so I can look at it myself? |
comment:20
The result of the added print is
To reproduce, I think this is enough:
|
comment:21
Ah I see the problem it is a unicode thing. If you do:
then everything should work. I will create a new ticket with a fix. |
comment:22
See #23822 |
comment:23
I am hurt by all this again when going from sage 8.4.beta0 to 8.4.beta1. |
comment:24
Hurt by what again? |
comment:25
I got build failures for sagelib on the very same line
but I have now realized that this is probably due to the existence of a personal "pip.conf". |
At #20913 pip was patched so that it works without ssl support, and this patch was also submitted upstream. Upstream has since merged the patch at pypa/pip#1165 into 9.0.1. So it makes sense to upgrade pip to this new version in order to have an unpatched pip in sage.
The pip tarbal can be found at https://pypi.python.org/packages/11/b6/abcb525026a4be042b486df43905d6893fb04f05aac21c32c638e939e447/pip-9.0.1.tar.gz#md5=35f01da33009719497f01a4ba69d63c9
Component: packages: standard
Author: Maarten Derickx
Branch:
b6b9954
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/23615
The text was updated successfully, but these errors were encountered: