-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Allow charset normalizer >=2 and <4 #6261
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's little value to raising the lower bound and much more grief for users
Yes, and given this isn't critical path for most users it's not critical to force people through a major version change to get that. If they use character detection of any sort and need performance they can force it to upgrade, but that's not our job |
Thanks @deedy5! |
Any estimation on a new release with this fix? |
git clean -xdf tar zcvf ../python-requests_2.28.1.orig.tar.gz --exclude=.git . debuild -uc -us cp python-requests.spec ../python-requests_2.28.1-1.spec mv ../python*-requests*2.28.1*.{gz,xz,spec,dsc} /osc/home\:alvistack/psf-requests-2.28.1 rm -rf ../python*-requests_2.28.1*.* See psf#6261 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
This should now be available on PyPI in Requests 2.28.2. |
We currently pin requests to version 2.27.1. This was last bumped in May of 2022 in 24808f0. Over time its version has been incremented a few times. Currently if you run tox you see an error like this: > /home/runner/work/consumerfinance.gov/consumerfinance.gov/.tox/unittest/lib/python3.8/site-packages/requests/__init__.py:102: RequestsDependencyWarning: urllib3 (1.26.15) or chardet (5.1.0)/charset_normalizer (2.0.12) doesn't match a supported version! For example, a recent GHA run: https://github.com/cfpb/consumerfinance.gov/actions/runs/4737203702/jobs/8409716743 I'm not entirely sure why this started showing up now, but it seems to have to do with psf/requests#6261. Removing our requests pin seems to work fine.
charset-normalizer 3.0.0 has been released.