Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

greenlet version < 2.0.0 #123

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

greenlet version < 2.0.0 #123

wants to merge 1 commit into from

Conversation

idot
Copy link

@idot idot commented Mar 31, 2021

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
benoitc/gunicorn#2541 (comment)

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 
benoitc/gunicorn#2541 (comment)
@bburtin
Copy link

bburtin commented Mar 31, 2021

Thanks for doing this!

lsix added a commit to lsix/nixpkgs that referenced this pull request Apr 6, 2021
Update greenlet to 1.0.0.

meinheld declares a dependency to greenlet <0.5, but according to [1]
and [2], there are no API or ABI changes leading to greenlet-1.0.0, so
it seems reasonable to drop the strict requirement.  This commit
uses substituteInPlace to patch setup.py since no upstream commit has
landed in the main branch yet.

Morehover, quoting [2]:

    Prior to greenlet 1.0 there were no semantic meanings attached to
    greenlet versions — API and ABI regularly changed from 0.4.x
    to 0.4.x+1, so their current pin doesn't make much sense anyway.

nix-review reveals few broken packages that are also broken in master.

[1] mopemope/meinheld#123
[2] benoitc/gunicorn#2541 (comment)
@hendrikmakait
Copy link

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
Copy link

bburtin commented Aug 3, 2021

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
Copy link

Any updates on a merge timeline?

@MikaYuoadas
Copy link

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

@aisk
Copy link

aisk commented Apr 25, 2022

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

@ibraheemalayan
Copy link

@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
Copy link

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
Copy link

aisk commented Jul 12, 2022

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
Copy link

@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
Copy link

luckydonald commented Oct 15, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants