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

Stuck on "Python is still starting up" for a while on Windows 7 #134

Closed
zakahmad opened this issue Oct 14, 2015 · 12 comments
Closed

Stuck on "Python is still starting up" for a while on Windows 7 #134

zakahmad opened this issue Oct 14, 2015 · 12 comments

Comments

@zakahmad
Copy link

I tried both 32-bit and 64-bit Win 7 installations. After launching Rodeo and waiting for more than an hour I still get the following message in the console when I try anything:

Could not execute command. Python is still starting up. This should only take another couple seconds.

I uninstalled 64-bit, installed 32-bit version and got the same message.
Under Preferences -> General, I changed the Default Python Command to "C:\Python27\python.exe" and also tried "C:\Python27" (output of os.path.dirname(sys.executable) is "C:\Python27"). None fixed the issue even after restarting Rodeo.

I'm not if there's more I can do on my end to make sure it's not my python installation that's rogue.

@olivierfriard
Copy link

This problem is also present on Debian 8.2 64 with v. 0.3.16.
Tried with /usr/bin/python and /usr/bin/python3.
No way to get out of "Could not execute command. Python is still starting up. This should only take another couple seconds."

@tinylucid
Copy link

I have the same problem on Windows 10 x64 running Python 3.5 only! :(

@PranY
Copy link

PranY commented Oct 19, 2015

same problem with windows 7 x64

@gamegoofs2
Copy link

I'm getting the same thing. Windows 8/Python 3.5 restarted Rodeo a couple times and still the same thing.

@ghost
Copy link

ghost commented Oct 23, 2015

Same here, win 7 x64 with python 3.5

@glamp
Copy link
Contributor

glamp commented Oct 28, 2015

@PranY @olivierfriard what version of python?

@glamp
Copy link
Contributor

glamp commented Oct 28, 2015

@zakahmad @olivierfriard @FilipMiletic @PranY @gython1 @gamegoofs2 Just to be sure this isn't the issue, can you try the following:

  1. Check your versions of jupyter, matplotlib, and pandas and report them here (might be the issue)
  2. re-installing/upgrading jupyter, matplotlib, and pandas and reopen Rodeo

Thanks!

@keberwein
Copy link

The above suggestion worked for me. I'm running Anaconda on OSX with a custom location set in my Rodeo prefs "/usr/local/bin/Python3"

I did a re-install of the jupyterhub, matplotlib and pandas using:
pip install --upgrade --force-reinstall <package_name>

@ottocapo
Copy link

Same problem here on Windows 7. Did anybody find a way to fix this issue?
Edit:
Still trying to install all the suggested packages, pandas itself has lots of requirements. Might need to install Visual studio as well.

@peeter-t2
Copy link

Maybe you could add a note to follow the installation instructions also onto the download page? Otherwise just clicking the .exe is too tempting and may lead to slight frustration.

Installing jupyter+matplotlib+pandas fixed it. Matplotlib needs Visual Studio too, it seems. The easiest way to install matplotlib was by downloading and installing Anaconda (see instructions).
Great work on the software btw, thanks for the effort!

@ottocapo
Copy link

ottocapo commented Jan 6, 2016

Absolutely. I forgot to comment but I got it to work after installing Anaconda. My bad.
Thanks to the developers!

@coristig
Copy link
Contributor

This is fixed in 1.3.0. The issue was with python paths having spaces in them.

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants