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

Gunicorn fails to run without `futures` #1200

Closed
robbles opened this Issue Feb 6, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@robbles

robbles commented Feb 6, 2016

Installing gunicorn 19.4.5 on OSX in a python 2.7 virtualenv yields the following error when I try to run it:

Error: class uri 'gunicorn.workers.gthread.ThreadWorker' invalid or not found:

[Traceback (most recent call last):
  File "/src/.venv/lib/python2.7/site-packages/gunicorn/util.py", line 142, in load_class
    mod = import_module('.'.join(components))
  File "/usr/local/Cellar/python/2.7.8_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/src/.venv/lib/python2.7/site-packages/gunicorn/workers/gthread.py", line 37, in <module>
    """)
RuntimeError:
    You need to install the 'futures' package to use this worker with this
    Python version.

]

Installing futures with pip install futures seems to fix the problem. There's no explanation of this in the README though, it just says pip install gunicorn is enough. Did I miss a step, or is there a missing dependency that's not being pulled in on install?

@benoitc

This comment has been minimized.

Show comment
Hide comment
@benoitc

benoitc Feb 6, 2016

Owner

Using python 3 skips the need to install the futures packages :)

In the mean time we should probably add a note to the doc too, you're right. I will patch it ASAP or if you want don't hesitate to send a patch. Thanks anyway 👍

Owner

benoitc commented Feb 6, 2016

Using python 3 skips the need to install the futures packages :)

In the mean time we should probably add a note to the doc too, you're right. I will patch it ASAP or if you want don't hesitate to send a patch. Thanks anyway 👍

@robbles

This comment has been minimized.

Show comment
Hide comment
@robbles

robbles Feb 6, 2016

@benoitc thanks for the quick response!

I think adding a note to the docs is enough. I'd send a PR, but it'll probably be more work for you than just changing it when you have time.

I suppose requiring one extra step to continue using python2.X is good motivation for people like me to get on with upgrading to 3.x 😄

robbles commented Feb 6, 2016

@benoitc thanks for the quick response!

I think adding a note to the docs is enough. I'd send a PR, but it'll probably be more work for you than just changing it when you have time.

I suppose requiring one extra step to continue using python2.X is good motivation for people like me to get on with upgrading to 3.x 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment