yhat / rodeo

A data science IDE for Python
Other
3.93k stars 410 forks source link

Rodeo Desktop dont start python #147

Open albahnsen opened 8 years ago

albahnsen commented 8 years ago

After initializing I got

IPython -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.
>>> 
Could not execute command. Python is still starting up. This should only take another couple seconds.
>>> 

I redirect in preferences the "Default Python Command" to

~ $ which python
/home/al/anaconda3/bin/python

But still the same issue.

There is no additional info when running from the command line

/usr/share/Rodeo $ ./Rodeo
[12912:1030/105630:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[12939:1030/105630:INFO:renderer_main.cc(200)] Renderer process started
[12931:1030/105631:ERROR:gles2_cmd_decoder.cc(11539)] [GroupMarkerNotSet(crbug.com/242999)!:D0464716FD330000]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command
[12912:1030/105631:INFO:CONSOLE(336)] "Uncaught Error: Cannot find module 'rimraf'", source: module.js (336)
[12912:1030/105631:INFO:CONSOLE(336)] "Uncaught Error: Cannot find module 'rimraf'", source: module.js (336)
[12912:1030/105631:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[12912:1030/105631:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[12912:1030/105631:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[12912:1030/105631:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[12912:1030/105631:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[12912:1030/105631:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
phillipboy07 commented 8 years ago

I was having the same issue as well, when I attempted to get Rodeo to work in Ubuntu. I followed @keberwein instructions, _I had the same problem on OSX. Reinstalling jupyter, matplotlib, and pandas solved this for me. pip install --upgrade --force-reinstall _ but the issue still existed. I clicked on View and selected "Toggle Dev Tools" and noticed there were some errors with npm modules. After I installed the missing modules, Python was working properly within Rodeo.

watsang commented 8 years ago

How can I find these missing npm modules?

albahnsen commented 8 years ago

@phillipboy07 can you elaborate more.

I did sudo apt-get install node-rimraf but node-rimraf is already the newest version.. Then I tried npm install rimraf and I got:

rimraf@2.4.3 node_modules/rimraf
└── glob@5.0.15 (path-is-absolute@1.0.0, inherits@2.0.1, once@1.3.2, inflight@1.0.4, minimatch@3.0.0)

But I still have the same issue. [15199:1110/115921:INFO:CONSOLE(336)] "Uncaught Error: Cannot find module 'rimraf'", source: module.js (336)

Thanks.

phillipboy07 commented 8 years ago

I would try "npm update" and restarting my computer.

On Tue, Nov 10, 2015 at 12:04 PM, Alejandro Correa Bahnsen < notifications@github.com> wrote:

@phillipboy07 https://github.com/phillipboy07 can elavorate more.

I did sudo apt-get install node-rimraf but node-rimraf is already the newest version.. Then I tried npm install rimraf and I got:

rimraf@2.4.3 node_modules/rimraf └── glob@5.0.15 (path-is-absolute@1.0.0, inherits@2.0.1, once@1.3.2, inflight@1.0.4, minimatch@3.0.0)

But I still have the same issue. [15199:1110/115921:INFO:CONSOLE(336)] "Uncaught Error: Cannot find module 'rimraf'", source: module.js (336)

Thanks.

— Reply to this email directly or view it on GitHub https://github.com/yhat/rodeo/issues/147#issuecomment-155488112.

phamkhactuy commented 8 years ago

I have proplem the same on Windows10. Do you have solution for issue?

albahnsen commented 8 years ago

@phillipboy07 it did not worked

hazam commented 8 years ago

this is problem also for me - I dont' see any errors in the dev console though