Incorrectly Detecting uWSGI

[skortchmark9]

Hey Miguel - thanks so much for your awesome work on this stuff.

I'm running flask-socketio but i think the recent change to this library is causing my problem.
I am running an app from manage.py under flask-script, and in the last two days when I attempt to start it up, I get:
INFO:engineio:Server initialized for gevent_uwsgi
And then it exits. Explicitly setting the async_mode='gevent' fixes the problem and returns the previous behavior.

Attached is my requirements.txt.

Flask
Flask-Migrate
Flask-SQLAlchemy
raven[flask]
greenlet==0.4.9
flask-socketio>=2.6.2
gevent
gevent-websocket
socketIO_client
gunicorn
supervisor
supervisor_twiddler
superlance
psycopg2
ipython
requests

[miguelgrinberg]

Can you run pip freeze and provide the output?

[skortchmark9]

alembic==0.8.7
astroid==1.4.8
backports.functools-lru-cache==1.2.1
backports.shutil-get-terminal-size==1.0.0
backports.ssl-match-hostname==3.5.0.1
blinker==1.4
click==6.6
configparser==3.5.0
contextlib2==0.5.4
coverage==4.2
decorator==4.0.10
Flask==0.11.1
Flask-Migrate==2.0.0
Flask-Script==2.0.5
Flask-SocketIO==2.6.2
Flask-SQLAlchemy==2.1
funcsigs==1.0.2
gevent==1.1.2
gevent-websocket==0.9.5
greenlet==0.4.9
gunicorn==19.6.0
ipython==5.1.0
ipython-genutils==0.1.0
isort==4.2.5
itsdangerous==0.24
Jinja2==2.8
lazy-object-proxy==1.2.2
Mako==1.0.4
MarkupSafe==0.23
mccabe==0.5.2
meld3==1.0.2
mock==2.0.0
pathlib2==2.1.0
pbr==1.10.0
pexpect==4.2.1
pickleshare==0.7.4
prompt-toolkit==1.0.7
psycopg2==2.6.2
ptyprocess==0.5.1
py==1.4.31
Pygments==2.1.3
pylint==1.6.4
pytest==3.0.1
pytest-cov==2.3.1
pytest-mock==1.2
python-editor==1.0.1
python-engineio==1.0.0
python-socketio==1.5.0
raven==5.25.0
requests==2.11.1
simplegeneric==0.8.1
six==1.10.0
socketIO-client==0.7.0
SQLAlchemy==1.0.14
superlance==0.11
supervisor==3.3.1
supervisor-twiddler==1.0.0
sx-hootl-gui2==0
traitlets==4.2.2
wcwidth==0.1.7
websocket-client==0.37.0
Werkzeug==0.11.10
wrapt==1.10.8

[miguelgrinberg]

@skortchmark9 you are not using the uwsgi web server, correct? That would explain this behavior, so I need to rule that out.

[skortchmark9]

Nope, using gevent and gevent-websocket