Closed moorepants closed 7 years ago
I was thinking about sympy@master to our anaconda channel, maybe under a dev label, don't know how to reference that in environment.yml though
dependencies:
- pip:
- https://github.com/sympy/sympy/archive/master.tar.gz
or if you want a specific commit,
dependencies:
- pip:
- https://github.com/sympy/sympy/archive/7efbee85cf49d767a11de8344b2b99b2b2460769.tar.gz
One of the packages in the env.yml seems to have a dependency on sympy, so removing sympy and adding this creates a double install of sympy.
It's python-symengine
-- I was actually thinking about just that.
That's interesting. It's sort of circular to have sympy be a dependency of python-symengine.
I was wrong, it's only the tests that actually require SymPy: https://github.com/conda-forge/python-symengine-feedstock/blob/master/recipe/meta.yaml
It is our own package... scipy2017codegen
, so easily fixed. I'm on it.
Now we have sympy@master in our binder environment. Thanks @isuruf!
I just realized that the Docker image that binder v2 comes with does not contain gcc. I'll add a separate environment.yml
called environment-binder.yml
which also lists gcc
as a dependency. Because I think most people prefer relying on system provided compilers, right?
Need to change to master.