Crashes with wsgi-env-behavior=holy

[ipmb]

We run a number of Python sites in separate uwsgi instances, both Python 2 and 3. After running into #1408 on one of our Python 3 apps, we set the wsgi-env-behavior to holy in all our uWSGI (v2.0.14) instances.

On a few (but not all) of our Python 2 instances, we started seeing #1111.

For now, we are running our Python 2 sites without the holy behavior and the Python 3 sites with it. I'm not clear whether or not this is the correct solution or if there is a deeper issue in uWSGI we're missing.

[a-feld]

@ipmb uWSGI v2.0.15 contains a fix which prevents the SystemError issue with wsgi-env-behavior set to cheat.

If you upgrade to v2.0.15 and set wsgi-env-behavior=cheat does that eliminate the SystemError?

[socketbox]

Can this be closed as a result of #2280 ?

[ipmb]

I'm no longer using uWSGI on any Python 2 projects, so I'm unable to confirm.