Skip to content

Commit

Permalink
Pin emperor install at 0.9.51
Browse files Browse the repository at this point in the history
Emperor is required by qiime with version reqs:

emperor<1.0.0,>=0.9.51

It turns out that the current version, 0.9.60 has a broken install, giving this
error on /modern/ pip:

    error in emperor setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Unordered types are not allowed

What's weird is that this apparently worked at some point with the historical install on Legion.  I guess something changed in pip/setuptools.

Legion [login07] ~ ☻ ➤ pip show emperor
Name: emperor
Version: 0.9.60
Summary: Emperor
Home-page: http://github.com/biocore/emperor
Author: Emperor development team
Author-email: yoshiki89@gmail.com
License: UNKNOWN
Location: /shared/ucl/apps/python/bundles/1507715676-2/venv/lib/python2.7/site-packages
Requires: numpy, qcli, scikit-bio
Legion [login07] ~ ☻ ➤
  • Loading branch information
owainkenwayucl committed Apr 11, 2018
1 parent e5de167 commit fb06b90
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions lists/python-2.list
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,6 @@ MACS2
MACS
mercurial
misopy
emperor==0.9.51
qiime
GromacsWrapper

2 comments on commit fb06b90

@owainkenwayucl
Copy link
Contributor Author

@owainkenwayucl owainkenwayucl commented on fb06b90 Apr 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this is related to the issue @ikirker opened here:

biocore/emperor#631

The problem is, although the developer acknowledges the issue and is fixing it in 1.x, qiime needs pre 1.x.

@owainkenwayucl
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've opened an issue with the qiime devs here:

biocore/qiime#2212

Please sign in to comment.