-
Notifications
You must be signed in to change notification settings - Fork 37
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
Testing omnia #103
Comments
I have a Jenkins test set up that tries to create The test gets as far as creating the 2.7 environment and trying to install I think this is because the |
The omnia metapackage includes pymbar, which prevents installation on py3X. I think the best immediate plan is to edit the omnia metapackage to:
|
I'm not sure that's the problem. If it were, it would install the python 2.7 versions of everything. Currently the |
AFAIK, I think the plan was to punt on py3K support for 1.0 (only for the metapackage). We should still build the various binaries for all python versions. |
So when I try to install, I do not get any prompt to upgrade python:
|
Try it on a Mac. |
By "punt on Python 3k", do you mean 3.x versions? |
If so, we should rebuild |
So I'm on my linux Desktop for now, so we'll need someone else to look into reproducing the OSX behavior. |
On os-x, |
Unclear to me why py34 is prefered though. |
I believe I have fixed this. |
What was required for the fix? Did you do a PR? |
No. I removed a broken file from https://binstar.org/omnia/pymbar/files. It was sorting higher, but didn't have a version of python declared. |
Ah, I see your comment in #125 now---thanks! |
Huh. Now we're downgrading everything to Python 2.7 when trying to install in a 3.x environment:
|
LOLLL. |
This is expected because of pymbar
|
Maybe this is the expected behavior, given that omnia requires pymbar, which hard-requires py27. |
I've tried to install packages with conda before that don't have a py34 version and it just says "unsatisfiable dependency" rather than uninstalling my version of python |
My guess is it may depend on whether you use a new or default environment?
|
Options
|
Emma also has py3k issues. On Thu, Jan 15, 2015 at 5:22 PM, Robert T. McGibbon <
|
Yeah, but it's not part of the current recipe for the omnia metapackage, so for this it doesn't matter. |
It looks like the current master branch of pymbar is tested on py34. Why not just cut another beta release, and then this will be fixed? |
2.1 beta is really not beta--it's the stable release. Whereas master On Thu, Jan 15, 2015 at 5:41 PM, Robert T. McGibbon <
|
I see. |
I've started to build a preliminary Jenkins-based omnia test:
https://jenkins.choderalab.org/job/test-conda-omnia-release-osx/
It creates a fresh
miniconda
installation and cycles through python 2.7, 3.3, and 3.4, creating a conda environment for each in which it attempts to installomnia
. We can add some simpleimport packagename
tests too.More generally, how should we actually test
omnia
? I think @frabjous5 was putting together some IPython notebooks that show off how to use multiple components ofomnia
together---can we use these as test scripts?The text was updated successfully, but these errors were encountered: