Upgrading to python3.6 from python2.7 in superset
See original GitHub issueMake sure these boxes are checked before submitting your issue - thank you!
- 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.25.6 to 0.28
Expected results
To use an easy way to upgrade python version from 2.7
to 3.6
of superset and superset version to 0.28
and keep all old data and information (Dashboard,Charts,Tables)
But the command is not working
pip install superset -- upgrade
superset db upgrade
Actual results
Can not smoothly upgrade the superset version to 0.28
Steps to reproduce
Just as the title said, is there an easy way to upgrade python version from 2.7
to 3.6
of superset and keep all old data and information (Dashboard,Charts,Tables) ?
I use the old version of superset is 0.25.6
and python is 2.7
for now.
And I want to upgrade to 0.28
for superset, but the version 0.28
is not support python2.7
.
I found that if use command pip install superset
would install at path /usr/local/lib/python2.7/dist-packages
and use command pip3 install superset
would install on path /usr/local/lib/python3.6/dist-packages
.
The old version of superset and data is at path python2.7
, but the new one will build at path python3.6
.
How can I move the old version of superset and data to new version?
Any help would be appreciated!
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top GitHub Comments
Would recommend using some sort of containerization, either something like Docker, or something like Python virtualenvs.
If you’re running Superset in production, you should have some sort of build mechanism that can rebuild a new box/instance/vm/… from scratch. The py3.6 install should probably not be done on top of the py2.7 install, but on a new box/instance/vm using the py3.6 build steps.
Finally, I solved the problem by using
virtualenv
and upgraded to version0.28.0
. There were some strange problems and error shown in the upgrading process, but they would solve by Google. Thanks for @mistercrunch reply.