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 scipy to 0.16.1 #17643
Comments
comment:1
Didn't know it was out. Not in the Gentoo tree yet so I have no idea so far. |
comment:2
scipy 0.16.0 is out, one doctest broken:
this is on top of 6.9.beta0. |
This comment has been minimized.
This comment has been minimized.
Branch: u/fbissey/scipy_0.16.1 |
Commit: |
Author: François Bissey |
New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
New branch compatible with the new push at #19556 coming soon. |
New commits:
|
Changed branch from u/fbissey/scipy_0.16.1 to u/fbissey/scipy-0.16.1 |
comment:12
Just a confirmation that with the three tickets applied all tests pass (debian 64bits). Could you replace
with
Or there is a reason to let it as you did? |
comment:13
No reason I didn't do that. I was so focused in finding a replacement for that particular line (it took some effort for me) that I didn't realise the code could be streamlined. |
comment:15
Replying to @kiwifb:
All done. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:24
Can you report it somewhere upstream? |
comment:25
I'll look into it. I am guessing it is technically a bug in |
comment:26
It looks like someone already acted in upstream |
comment:27
I think I might have removed the |
comment:28
Replying to @jpflori:
The danger with those two scenario is that the removal will be forgotten. However considering that everyone else has it with some variations (Gentoo has |
Changed branch from u/fbissey/scipy-0.16.1 to |
comment:30
I must say I spent a bit of my night worrying that it was the wrong fix. Good that it really works. |
Changed commit from |
comment:31
Argh still doesn't work... http://build.sagedev.org/release/builders/%20%20slow%20Oxford%20ARM%20%28Ubuntu%2012.10%29%20incremental/builds/330/steps/compile/logs/scipy Last 10 new commits:
|
Changed branch from |
Commit: |
comment:32
OK so I was right to worry it was the wrong fix. I'll remove the last commit on the scipy branch and add the upstream commit in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/fbissey/scipy-0.16.1 to |
Upgrade to scipy 0.16.1 this is intended to be done at the same time as numpy 1.10.1 and matplotlib 1.5.0 as noted in the ticket dependencies.
http://www.lmona.de/files/sage/scipy-0.16.1.tar.gz
Component: packages: standard
Author: François Bissey
Branch/Commit:
cc6accc
Reviewer: Volker Braun
Issue created by migration from https://trac.sagemath.org/ticket/17643
The text was updated successfully, but these errors were encountered: