-
Notifications
You must be signed in to change notification settings - Fork 9
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
Streamline builds in preparation for Python 3.7 #143
Conversation
Missed a flag in the OpenMM `build.sh` file which pointed to the CUDA 9.0 image, which does not exist right now since we build with 9.1 cc @jchodera
|
||
) | ||
p.add_argument( | ||
'--numpy', | ||
help="Set the NumPy version used by conda build", | ||
metavar="NUMPY_VER", | ||
default='1.10,1.11,1.12', | ||
default='1.13,1.14,1.15', |
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.
@Lnaden : It looks like conda-forge is actively building numpy 1.9, 1.11, and 1.15 for Python 3.7 now:
https://anaconda.org/conda-forge/numpy/files
They're have also built numpy 1.10, 1.12, 1.13, and 1.14 for Python 2.7, 3.5, and 3.6.
This is a pretty weird combination.
@Lnaden : I've tried to update the build infrastructure to build against the numpy versions available for each Python version on conda-forge. |
Thats fine. I tried to make as minimal changes as we need to. Honestly, we could probably (and should) remove that bit since none of our packages use the |
Good point! |
Looks like conda-forge hasn't started building some of our dependencies for Python 3.7 yet, so this might have to hold for a bit:
|
I think you can safely unpin from sphinx 1.5.6 per the PR I have here on the main conda-recipes channel. Just make sure its at least that to avoid other odd backwards compatibility issues |
@Lnaden: For reference, unpinning
|
The problem now is that there appear to be no |
Start builds against Python 3.7 for testing