Skip to content
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

Install request: MDAnalysis #135

Closed
ikirker opened this issue Dec 20, 2017 · 2 comments
Closed

Install request: MDAnalysis #135

ikirker opened this issue Dec 20, 2017 · 2 comments

Comments

@ikirker
Copy link
Contributor

ikirker commented Dec 20, 2017

From: IN:02748765

MDAnalysis and its tests package MDAnalysisTests install easily off pip. It depends on numpy and some other things, and fails a few of its unit tests on Python 3 (ones around universal density), and once you manage to find the note saying that Python 3 support is experimental, that's not surprising. It succeeds with Python 2.7.12, so it'll just go in the Python 2 list of packages.

Unfortunately installing this is currently stuck behind biocore/emperor#631 because of the way we build Python environments: we rebuild the whole Python environment (i.e. reinstall all packages in the bundle) whenever the list of packages changes, and because emperor won't install, we can't update the Python 2 bundle, as emperor is installed as a dependency of QIIME and QIIME is only installed with Python 2.

The current version of emperor was installed from a wheel, I think, but that wheel doesn't seem to exist anymore?

From a user usage perspective, we can't just remove emperor because that would remove/break QIIME, so if any of our users are using that, their jobs would suddenly break, and we could pin the version down to a previous one in the list, but that would expose them to old bugs.

I guess this is our fault for not having made a plan for if this sort of thing happens. 😞

@ikirker
Copy link
Contributor Author

ikirker commented Dec 22, 2017

The fix for emperor is now in, but we'll still need to wait for a new release version to appear in PyPi, or else use pip install --pre (not recommended).

@ikirker
Copy link
Contributor Author

ikirker commented Jun 15, 2018

Reviewed this and the associated ticket; user is running this on their own local machine instead, and said they'll contact us again if they need it on the cluster. 🤷‍♀️

So, closing.

@ikirker ikirker closed this as completed Jun 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant