Riccardo Magliocchetti

It's `-Wdeprecated-declarations` that should be disabled (via `-Wno-error=deprecated-declarations`) on uwsgi-2.0 branch. Maybe it's not disabled in plugin building path. How did you built uwsgi? Anyway uwsgiconfig.py is where the build...

I cherry-picked the two commits in the middle, taking a look at the others will require a bit

@velis74 you should probably get some hints in uwsgi log. I'll give it a try removing selectively the following configurations: post-buffering = 1 harakiri = 300 max-worker-lifetime = 35

@joekohlsdorf have you tried enlarging the listen queue? gunicorn one is like 20x times the uwsgi default.

@ryankask is this still an issue? btw if you are doing pubsub the redis-py's pubsub object has a run_in_thread method to help you with this.

Looks like an issue with your python: ` ld: in /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o), could not parse object file /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o): 'Unknown attribute kind (61) (Producer: 'LLVM10.0.0' Reader: 'LLVM APPLE_1_1001.0.46.4_0')', using libLTO version 'LLVM...

@rdeioris I'll take a look at max-requests-delta later today. Regarding gevent the fix is already merged both in master and uwsgi-2.0 since a few.

That file is used by pypy and not by cpython. Said that it's using imp.load_source which has been removed in python3 since a few.

I guess that it was resolved as pyscopg2 > 2.8 is now a source package so the libssl it is linking against is the very same of uwsgi.

Have you checked this is not a python behaviour change? You changed three major version of python.