greenlet version < 2.0.0

[idot]

greenlet < 0.5 conflicts with SQLAlchemy 1.4 which installs greenlet 1.0 the greenlet API should not have changed between 0.5 and < 2 according to https://github.com/benoitc/gunicorn/issues/2541#issuecomment-800353993

[bburtin]

Thanks for doing this!

[hendrikmakait]

I'm running into the version mismatch as well, are there any plans to merge this PR soon or should we find an alternative for now?

[bburtin]

Any chance that we can get this merged? I hit some esoteric bugs in SQLAlchemy 1.3 and would like to upgrade to the latest version. Thanks!

[OneWithTheCore]

Any updates on a merge timeline?

[MikaYuoadas]

We're having the same version mismatch issue with gevent.

[aisk]

Hi what's to do before we merge this PR?

[ibraheemalayan]

@mopemope it has been a lot of time and this fix has not been merged yet, checks have passed, could you merge it or find a solution, because the conflict with SQLAlchemy is a huge issue for a lot of projects

[ibraheemalayan]

Until this PR gets merged, a temporal solution would be to install the package from the patched branch provided by @idot

pip3 install  --user git+https://github.com/idot/meinheld.git@patch-1

[aisk]

Until this PR gets merged, a temporal solution would be to install the package from the patched branch provided by @idot

pip3 install  --user git+https://github.com/idot/meinheld.git@patch-1

This should work, but I recommend using commit hash instead of branch for security reasons.

[KohakuBlueleaf]

@mopemope Do you still maintain this project now? There are 2 PRs which looks good and actually fix some problems. And you just leave them about 1yr.

[luckydonald]

This should work, but I recommend using commit hash instead of branch for security reasons.

You can do that like this:

pip3 install git+https://github.com/idot/meinheld.git@2bfe452d6608c92688d92337c87b1dd6448f4ccb

Also note that I've omitted that --user flag, as I'm using virtualenv anyway.