- #INSTALL REQUESTS FOR PYTHON 3 OSX INSTALL#
- #INSTALL REQUESTS FOR PYTHON 3 OSX SOFTWARE#
- #INSTALL REQUESTS FOR PYTHON 3 OSX LICENSE#
#INSTALL REQUESTS FOR PYTHON 3 OSX INSTALL#
You should consider upgrading via the 'pip install -upgrade pip' command. You are using pip version 6.1.1, however version 9.0.1 is available.
#INSTALL REQUESTS FOR PYTHON 3 OSX SOFTWARE#
I've read, , and so I'm aware of the history, but I hope that the approach in this PR will allow this to be merged, as right now, the Apache Software Foundation doesn't allow projects to depend upon LGPL'd code (this is something I'm trying to get changed, but it is a very slow process)Įxample with pip 6.1.1 (but same with pip 8.1.1): > pip install requests (In my non-exhaustive tests it detects the same encoding as chartdet in every case I threw at it)
This should minimize the impact to users, and give them an escape hatch if charset_normalizer turns out to be not as good.
#INSTALL REQUESTS FOR PYTHON 3 OSX LICENSE#
By including an LGPL'd module it is no longer clear if the resulting artefact must also be LGPL'd.īy changing out this dependency for one under MIT we remove all license ambiguity.Īs an "escape hatch" I have made the code so that it will use chardet first if it is installed, but we no longer depend upon it directly, although there is a new extra added, requests. Ssl.SSLError: certificate verify failed (_ssl.c:600)ĭuring handling of the above exception, another exception occurred:Īt least for Python 3 - charset_normalizer doesn't support Python2, so for that chardet is still used - this means the "have chardet" path is also still tested.Īlthough using the (non-vendored) chardet library is fine for requests itself, but using a LGPL dependency the story is a lot less clear for downstream projects, particularly ones that might like to bundle requests (and thus chardet) in to a single binary - think something similar to what docker-compose is doing.
Return context.wrap_socket(sock, server_hostname=server_hostname)įile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/ssl.py", line 364, in wrap_socketįile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/ssl.py", line 578, in _init_įile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/ssl.py", line 805, in do_handshake $ python -c 'import requests print(requests.get(""))'įile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 544, in urlopenįile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 341, in _make_requestįile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 762, in _validate_connįile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 238, in connectįile "/Users/rmcgibbo/miniconda/envs/3.4.2/lib/python3.4/site-packages/requests/packages/urllib3/util/ssl_.py", line 256, in ssl_wrap_socket A get() request seems to work fine with requests-2.5.1, but after upgrading to requests 2.5.2, the same URL leads to CERTIFICATE_VERIFY_FAILED.
0 kommentar(er)
