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

fabmanager create-admin --app superset: Was unable to import superset Error: No module named 'retry' #7243

Closed
rjurney opened this issue Apr 8, 2019 · 2 comments
Labels
inactive Inactive for >= 30 days

Comments

@rjurney
Copy link
Contributor

rjurney commented Apr 8, 2019

Make sure these boxes are checked before submitting your issue - thank you!

Note: I can not find the superset logs nor where they are found in a web search. - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.

  • [* ] I have reproduced the issue with at least the latest released version of superset.
  • [* ] I have checked the issue tracker for the same issue and I haven't found one similar.

Superset version

0.28.1

Expected results

retry should be installed as part of pip install

Actual results

retry fails to install and must be installed manually

Steps to reproduce

pip install superset

Platform

Linux 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful

@rjurney rjurney changed the title pip install: Was unable to import superset Error: No module named 'retry' fabmanager create-admin --app superset: Was unable to import superset Error: No module named 'retry' Apr 8, 2019
@stale
Copy link

stale bot commented Jun 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Jun 7, 2019
@mistercrunch
Copy link
Member

0.28.1 has numerous issues with version ranges that had functioning release at the time it came out, but slipped in a bad place. Now we recommend installing from source and running pip install -r requirements.txt to get the pinned deps that we test against.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

2 participants