Closed peterbarker closed 8 years ago
Hi @peterbarker
cp: can't stat '/usr/lib/python2.7/site-packages/greenlet*': No such file or directory
D:\Github\solodevguide\examples\webserver>solo script run server.py
connecting to solo...
checking pip...
uploading script bundle...
./
./requirements.txt
./server.py
./static/
./static/jquery.min.js
./static/socket.io.min.js
./templates/
./templates/index.html
Not deleting env/bin
New python executable in env/bin/python
Installing setuptools, pip, wheel...done.
cp: can't stat '/usr/lib/python2.7/site-packages/greenlet*': No such file or directory
Ignoring indexes: https://pypi.python.org/simple
Requirement './wheelhouse/*.whl' looks like a filename, but the file does not exist
*.whl is not a valid wheel filename.
running script...
Traceback (most recent call last):
File "/log/solo-script/server.py", line 1, in <module>
from flask import Flask, render_template
ImportError: No module named flask
Does this have any other "implications"? Ie why was greenlets used in the first place?
greenlets were backing the eventlets.
The "cp" of the greenlet files should go away once we verify no other example is using it. Or possibly juts right now.
Your "pack" appears to be missing every wheel, not just flask. Can you present the listing of files in solo-sript.tar.gz, please?
I do not know why someone went to the trouble of using greenlets - the "cp" hack shows it was not a natural thing to do. They will probably have better performance than standard threading, but they do have the disadvantage of... not working on Solo ATM.
I've sent you the tar. You're right - wheels are missing.
The tar issue fixed by https://github.com/3drobotics/solo-cli/pull/40
@peterbarker
Example runs and install. Two issues to fix before can merge (that I will leave with you):
* Running on http://0.0.0.0:8080/ (Press CTRL+C to quit)
Would be better if it said:
* Connect to on http://10.1.1.10:8080/ on your browser (Press CTRL+C to quit)
FYI, I suspect the reason they went greenlets would be this note int he output:
WebSocket transport not available. Install eventlet or gevent and gevent-websocket for improved performance.
* Running on http://0.0.0.0:8080/ (Press CTRL+C to quit)
is not our message.
Will patch the docs.
I was running the Webserver example and received the errors that this pr looks to fix. I was just curious if it will be merged.
thanks @peterbarker
Fixes #287