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
Error when new PIP resolved accesses Oauthlib data #744
Comments
I tried |
Maybe ytou can remove/yank the offending library version ? I can also try to add limitation to oauthlub in our case! |
Try |
Confirmed by PIP developers that yanking this version should fix it. pypa/pip#9203 (comment) Would the maintainers be so kind to yank it? |
If you guys can yank (https://pypi.org/help/#yanked) that release, it should help us at Airflow and hopefully more libraries like us to use the new PIP resolver without error. Really appreciate all the work you guys are doing |
Hi, |
Thanks, appreciate that 🙏 |
Thanks a lot ! Really appreciate. Unfottunately, despite PIP maintainer confirmation, it did not work: pypa/pip#9203 (comment) Feel free to unyank @JonathanHuot |
Just update - don't unyank it please yet :). Seems that fix is coming pypa/pip#9226 |
Looks like this is fixed now (tested using pip 21.0) |
Thanks for letting us know :) |
@JonathanHuot Did we unyank the release yet? |
I have unyanked the release, if someone could confirm it still work, that will be great :) |
Works :) |
Describe the bug
In Airflow, we are experiencing problems when we are trying to use the PIP released 2 days ago which has the new resolver on by default.
ERROR: Requested oauthlib[signedtoken]>=1.0.0 from https://files.pythonhosted.org/packages/e5/54/4f96c51b171cf3a64a04b8c5167268803205bc5943b5cdf70bd770727b88/oauthlib-1.1.0-1.tar.gz#sha256=0f786c5573248a38efa86c48c59c0c93140ac836ab2a246aeefd8f9039e999ba (from jira->apache-airflow==1.10.13) has different version in metadata: '1.1.0'
How to reproduce
pip install --upgrade pip
pip --version
should return 20.3Apparently, metadata in published oauthlib 1.1.0-1 is wrong snd points to 1.1.0.
The same command with the legacy resolver works fine:
Expected behavior
I expect the resolver does not get broken by broken metadata.
Opened similar issue in PIP pypa/pip#9203 as I am not sure who can fix it.
The text was updated successfully, but these errors were encountered: