-
Notifications
You must be signed in to change notification settings - Fork 368
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
Switch cvxopt usage to cvxpy #430
Conversation
This commit switches the usage of cvxopt to use cvxpy instead.
It looks like a numpy release earlier today is causing the python 3.5 failure on windows. |
@mtreinish how can we make test pass? |
I'm hoping it was just a temporary packaging issue because of the new version that would sort itself today. If that doesn't work we can just set a cap on the python 3.5 job. |
This reverts commit 27d3062.
This reverts commit c862c6d.
The last numpy version with 3.5 support is below the minimum version of numpy that cvxpy requires. This leads to a situation where we try updating the conda install numpy with pip, and that causes things to break. This isn't an issue on python >=3.6 because the conda packages for numpy are kept up to date.
I was actually wrong as to the root cause, it was an artifact of conda vs pip. I wrote down the details of what's going on in: bde0e77 Hopefully that will work, I seem to remember that we needed to conda install numpy to get aer to compile in the windows jobs, but we'll see if that's an issue I guess. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Summary
This commit switches the usage of cvxopt to use cvxpy instead.
Details and comments