In this case, you've somehow installed the 2.x version of ndg-httpsclient into /usr/local/Cellar/python3/3.4.2_1/Frameworks/amework/Versions/3.4/lib/python3.4/site-packages. ![]() A standard Homebrew 3.x looks in two extra site-packages directories (fire up python3 then import sys print(sys.path) to see all of the places it looks, both stdlib and site) beyond the one that pip3 installs into. Underlying that, you've actually got two different Python 2.7 installations (Apple's and Homebrew's) crossed with each other, which may have something to do with how you got a 2.7 package into 3.x as well…Īnyway, the reason this is breaking pip is that pip has various optional dependencies that it tries to import if present, and some of them do the same, and so on, and ultimately, starting up pip is importing the ndg-httpsclient package. The root problem is that you somehow got a Python 2.x-only package installed into your 3.x site-packages. Python 2.7.5 (default, Mar 9 2014, 22:15:05)Ī lot of the other answers related to updating pip3 suggest that I update pip3 with this commend pip3 install -upgrade pip which gives the same error, or I use easy_install -U pip but because of how brew sets up the Pythons, it only updates the Python 2.7.5 version (there is no easy_install3). Type "help", "copyright", "credits" or "license" for more information. Just for sanity purposes Here is what when I see when I enter the interactive interpreters: $ python3 When I run the Python 2.7.5 version I see this: $ pip -version import pyopensslįile "/usr/local/lib/python3.4/site-packages/pip/_vendor/requests/packages/urllib3/contrib/pyopenssl.py", line 49, in įrom _peer_verification import SUBJ_ALT_NAME_SUPPORTįile "/usr/local/Cellar/python3/3.4.2_1/Frameworks/amework/Versions/3.4/lib/python3.4/site-packages/ndg/httpsclient/ssl_peer_verification.py", line 17 When I run pip3 -version (or anything related to the pip3 command) I see this: $ pip3 -versionįile "/usr/local/lib/python3.4/site-packages/pip/_init_.py", line 11, in įrom pip.vcs import git, mercurial, subversion, bazaar # noqaįile "/usr/local/lib/python3.4/site-packages/pip/vcs/mercurial.py", line 9, in įile "/usr/local/lib/python3.4/site-packages/pip/download.py", line 22, in įile "/usr/local/lib/python3.4/site-packages/pip/_vendor/requests/_init_.py", line 53, in įrom. Python packages installed by the python setup.py install command Ĭustom Python packages, that actually do not need to be installed but only copied in the DSS Python libraries folder.This all began when I set out to install the Requests library for Python 3 (I'm running on OSX Mavericks with Python 2.7.5 (installed by brew install python) and 3.4.2 (installed by brew install python3). The additional Python packages installed by DATA_DIR/bin/pip or added to DATA_DIR/lib/python are preserved by DSS upgrades. We upgrade these dependencies of DSS when releasing a new version, after they are properly qualified and we made sure everything works together. Notably, you must not change the version of the pandas, numpy and scikit-learn packages in the built-in environment. Modifying the version of these packages is not supported and may result in causing DSS to stop functioning. If you require another version of Python, please use a code environment.Ī number of packages are preinstalled in the built-in environment. The built-in Python environment uses Python 2.7, 3.6 or 3.7, as chosen at installation time. Importantly, this implies that in order to install packages in the built-in environment, you must NOT use the pip or python commands of your system, but use the pip or python commands of the DSS virtualenv. ![]() The built-in Python environment uses the Python virtualenv mechanism. ![]() ![]() Please pay attention to the following notes: API Node & API Deployer: Real-time APIs.Automation scenarios, metrics, and checks.Installing a “python setup.py install” package.Installing in the built-in DSS environment (not recommended).Installing in a specific code environment (recommended).
0 Comments
Leave a Reply. |