Pip install conda error

pip installation failed with ‘contains unsafe path’ error #8423

Current Behavior

Running conda install pip in an environment produces an error

Steps to Reproduce

Expected Behavior

Pip installs successfully.

Environment Information

`conda config —show-sources`

`conda list —show-channel-urls`

The text was updated successfully, but these errors were encountered:

I got a similar error when I tried to create a new environment, except the unsafe path was bin/python

Hey I had the same issue which seemed to be due to the anaconda distribution being installed on a different partition as the cwd one.

At least for me, moving to the same partition as anaconda’s solved the problem.

@cphyc Thank you for figuring this out. That solved my problem. Though, one should change the directory( cd ) into the desired environment path, not the path where anaconda is installed.

I got this issue installing pyopencl which requires you symlink $ANACONDAROOT/etc/OpenCL/vendors to your system opencl headers (e.g. /usr/include/CL). I did that and when I tried to conda install pyopencl I got

CondaFileIOError: ‘/usr/pubsw/packages/python/anaconda3-2019.03/pkgs/ocl-icd-2.2.12-h14c3975_1003.tar.bz2’. contains unsafe path: etc/OpenCL/vendors/.conda_keep

I think this should be possible. I worked around by copying over /usr/include/CL instead since it is small

I’ve had a couple users of our software running into this error when creating an environment with a prefix on a different partition than the installation. Shouldn’t this be possible and didn’t this work in previous releases?

Or am I just being dense?

@jasercion I frequently create environments with a prefix on a different partition than the conda installation. That in itself doesn’t cause the problem. In my case, the issue only ever occurred when conda was installed somewhere on the network (not locally) and I was running it from a different partition. I have found the best way to avoid the error is to install conda locally, not on a network disk.

@zkaufman Ah, gotcha. IIRC in our error case the users are using a distributed computing environment so it sounds like that is in fact the root cause.

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   — What OS and version you reproduced the issue on
   — What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Источник

pip installation failed with ‘contains unsafe path’ error #8423

Current Behavior

Running conda install pip in an environment produces an error

Steps to Reproduce

Expected Behavior

Pip installs successfully.

Environment Information

`conda config —show-sources`

`conda list —show-channel-urls`

The text was updated successfully, but these errors were encountered:

I got a similar error when I tried to create a new environment, except the unsafe path was bin/python

Hey I had the same issue which seemed to be due to the anaconda distribution being installed on a different partition as the cwd one.

At least for me, moving to the same partition as anaconda’s solved the problem.

@cphyc Thank you for figuring this out. That solved my problem. Though, one should change the directory( cd ) into the desired environment path, not the path where anaconda is installed.

I got this issue installing pyopencl which requires you symlink $ANACONDAROOT/etc/OpenCL/vendors to your system opencl headers (e.g. /usr/include/CL). I did that and when I tried to conda install pyopencl I got

CondaFileIOError: ‘/usr/pubsw/packages/python/anaconda3-2019.03/pkgs/ocl-icd-2.2.12-h14c3975_1003.tar.bz2’. contains unsafe path: etc/OpenCL/vendors/.conda_keep

I think this should be possible. I worked around by copying over /usr/include/CL instead since it is small

I’ve had a couple users of our software running into this error when creating an environment with a prefix on a different partition than the installation. Shouldn’t this be possible and didn’t this work in previous releases?

Or am I just being dense?

@jasercion I frequently create environments with a prefix on a different partition than the conda installation. That in itself doesn’t cause the problem. In my case, the issue only ever occurred when conda was installed somewhere on the network (not locally) and I was running it from a different partition. I have found the best way to avoid the error is to install conda locally, not on a network disk.

@zkaufman Ah, gotcha. IIRC in our error case the users are using a distributed computing environment so it sounds like that is in fact the root cause.

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   — What OS and version you reproduced the issue on
   — What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Источник

pip install fails in conda create virtual environments (but not in base environment) #8691

I am trying to pip install packages into conda virtual environments (i.e. ones created with conda create ) and getting

(this happens whether I try to install a package from pypi like black, or directly from a git repo via git+ssh (my actual end-goal).

I am able to pip install in the base environment, but I cannot pip install in environments created by conda create . I can also pip install into environments that were created with venv / virtualenv .

I’ve done a bit of digging into this issue. It usually happens to me when I’m behind a corporate firewall, but I’m not at the moment.

This is the closest thing I’ve been able to find to the problem I’m running into. The OP said that they resolved the issue by no longer creating virtual environments on remote drives. This makes me think that this might have something to do with the fact that I’m running this on WSL Ubuntu.

Any idea what the issue might be?

Thanks either way 🙂

p.s.
If I have time, I’ll try reproducing this on another windows computer.

Steps to Reproduce

Environment Information

Base `conda info`: «` active environment : base active env location : /home/zdufour/miniconda3 shell level : 1 user config file : /home/zdufour/.condarc populated config files : conda version : 4.6.14 conda-build version : not installed python version : 3.7.3.final.0 base environment : /home/zdufour/miniconda3 (writable) channel URLs : https://repo.anaconda.com/pkgs/main/linux-64 https://repo.anaconda.com/pkgs/main/noarch https://repo.anaconda.com/pkgs/free/linux-64 https://repo.anaconda.com/pkgs/free/noarch https://repo.anaconda.com/pkgs/r/linux-64 https://repo.anaconda.com/pkgs/r/noarch package cache : /home/zdufour/miniconda3/pkgs /home/zdufour/.conda/pkgs envs directories : /home/zdufour/miniconda3/envs /home/zdufour/.conda/envs platform : linux-64 user-agent : conda/4.6.14 requests/2.21.0 CPython/3.7.3 Linux/4.4.0-17763-Microsoft ubuntu/18.04.1 glibc/2.27 UID:GID : 1000:1000 netrc file : None offline mode : False «`

`conda config —show-sources`

`conda list —show-channel-urls`

«` # packages in environment at /home/zdufour/miniconda3: # # Name Version Build Channel anaconda-client 1.7.2 py37_0 defaults anaconda-project 0.8.2 py37_0 defaults appdirs 1.4.3 pypi_0 pypi asn1crypto 0.24.0 py37_0 defaults astroid 2.2.5 pypi_0 pypi attrs 19.1.0 py37_1 defaults black 19.3b0 pypi_0 pypi ca-certificates 2019.1.23 0 defaults certifi 2019.3.9 py37_0 defaults cffi 1.12.2 py37h2e261b9_1 defaults chardet 3.0.4 py37_1 defaults click 7.0 pypi_0 pypi clyent 1.2.2 py37_1 defaults conda 4.6.14 py37_0 defaults cryptography 2.6.1 py37h1ba5d50_0 defaults decorator 4.4.0 py37_1 defaults filelock 3.0.10 pypi_0 pypi idna 2.8 py37_0 defaults ipython_genutils 0.2.0 py37_0 defaults isort 4.3.20 pypi_0 pypi jsonschema 3.0.1 py37_0 defaults jupyter_core 4.4.0 py37_0 defaults lazy-object-proxy 1.4.1 pypi_0 pypi libedit 3.1.20181209 hc058e9b_0 defaults libffi 3.2.1 hd88cf55_4 defaults libgcc-ng 8.2.0 hdf63c60_1 defaults libstdcxx-ng 8.2.0 hdf63c60_1 defaults mccabe 0.6.1 pypi_0 pypi nbformat 4.4.0 py37_0 defaults ncurses 6.1 he6710b0_1 defaults openssl 1.1.1b h7b6447c_1 defaults pip 19.0.3 py37_0 defaults pluggy 0.11.0 pypi_0 pypi py 1.8.0 pypi_0 pypi pycosat 0.6.3 py37h14c3975_0 defaults pycparser 2.19 py37_0 defaults pylint 2.3.1 pypi_0 pypi pyopenssl 19.0.0 py37_0 defaults pyrsistent 0.14.11 py37h7b6447c_0 defaults pysocks 1.6.8 py37_0 defaults python 3.7.3 h0371630_0 defaults python-dateutil 2.8.0 py37_0 defaults pytz 2019.1 py_0 defaults pyyaml 5.1 py37h7b6447c_0 defaults readline 7.0 h7b6447c_5 defaults requests 2.21.0 py37_0 defaults ruamel_yaml 0.15.46 py37h14c3975_0 defaults setuptools 41.0.0 py37_0 defaults six 1.12.0 py37_0 defaults sqlite 3.27.2 h7b6447c_0 defaults tk 8.6.8 hbc83047_0 defaults toml 0.10.0 pypi_0 pypi tornado 6.0.2 py37h7b6447c_0 defaults tox 3.11.1 pypi_0 pypi tox-conda 0.2.0 pypi_0 pypi traitlets 4.3.2 py37_0 defaults typed-ast 1.3.5 pypi_0 pypi urllib3 1.24.1 py37_0 defaults virtualenv 16.6.0 pypi_0 pypi wheel 0.33.1 py37_0 defaults wrapt 1.11.1 pypi_0 pypi xz 5.2.4 h14c3975_4 defaults yaml 0.1.7 had09818_2 defaults zlib 1.2.11 h7b6447c_3 defaults «`

The text was updated successfully, but these errors were encountered:

Источник

Cannot install packages with either pip or conda #10576

Here is what is happening when I try using pip to install something:

pip install pymsgbox
pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Collecting pymsgbox
Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»)’: /simple/pymsgbox/
Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»)’: /simple/pymsgbox/
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»)’: /simple/pymsgbox/
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»)’: /simple/pymsgbox/
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»)’: /simple/pymsgbox/
Could not fetch URL https://pypi.org/simple/pymsgbox/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host=’pypi.org’, port=443): Max retries exceeded with url: /simple/pymsgbox/ (Caused by SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»)) — skipping
Could not find a version that satisfies the requirement pymsgbox (from versions: )
No matching distribution found for pymsgbox
pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host=’pypi.org’, port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»)) — skipping

here is what happened when I try the same thing with Conda:

conda install pymsgbox
Solving environment: failed
CondaHTTPError: HTTP 000 CONNECTION FAILED for url https://repo.anaconda.com/pkgs/r/noarch/repodata.json.bz2
Elapsed: —

An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.

If your current network has https://www.anaconda.com blocked, please file
a support request with your network engineering team.

SSLError(MaxRetryError(‘HTTPSConnectionPool(host=’repo.anaconda.com’, port=443): Max retries exceeded with url: /pkgs/r/noarch/repodata.json.bz2 (Caused by SSLError(«Can’t connect to HTTPS URL because the SSL module is not available.»))’))

Here is my system information:
Windows 10, 64bit
Dell Inspiron 13 7000
Python 3.7.1
conda 4.5.12

Any idea what may be causing this? I just need a way to install files. I am a beginner to this stuff so please explain things as clearly as possible.

The text was updated successfully, but these errors were encountered:

Источник

pip install not working #823

I make a new environment with pip and setuptools then try to install something trivial and it fails with the message setuptools must be installed to install from a source distribution . I’ve lately had to bootstrap install setuptools and pip every time I want to use pip.

> condactivate py27 (py27)

> pip install brewer2mpl Downloading/unpacking brewer2mpl Downloading brewer2mpl-1.4.tar.gz Storing download in cache at ./Library/Caches/pip-downloads/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2Fb%2Fbrewer2mpl%2Fbrewer2mpl-1.4.tar.gz Cleaning up. setuptools must be installed to install from a source distribution Storing debug log for failure in /Users/jiffyclub/.pip/pip.log»>

The text was updated successfully, but these errors were encountered:

This worked for me:

Nope, same problem for me:

> condactivate py27 (py27)

> type pip pip is /Users/jiffyclub/miniconda3/envs/py27/bin/pip (py27)

> pip install brewer2mpl Downloading/unpacking brewer2mpl Using download cache from /Users/jiffyclub/Library/Caches/pip-downloads/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2Fb%2Fbrewer2mpl%2Fbrewer2mpl-1.4.tar.gz Cleaning up. setuptools must be installed to install from a source distribution Storing debug log for failure in /Users/jiffyclub/.pip/pip.log»>

I assume condactivate is source activate .

First try doing conda update conda

Then if that fails send in what conda info says.

> conda info Current conda install: platform : osx-64 conda version : 3.5.5 python version : 3.4.1.final.0 root environment : /Users/jiffyclub/miniconda3 (writable) default environment : /Users/jiffyclub/miniconda3 envs directories : /Users/jiffyclub/miniconda3/envs package cache : /Users/jiffyclub/miniconda3/pkgs channel URLs : http://repo.continuum.io/pkgs/free/osx-64/ http://repo.continuum.io/pkgs/pro/osx-64/ config file : None is foreign system : False

hmm I’m using the python 2.7 one. let me check the 3.4 version.

Everything works for me with a fresh install of miniconda v 3.4.

Can you move your

/.pip_bk and remove the cached download:

This is the crux of the problem, I think:

> condactivate py27 (py27)

> python -c ‘import setuptools’ Traceback (most recent call last): File » «, line 1, in ImportError: No module named setuptools»>

It works fine if I do the same thing but in a python 3.4 environment instead of python 2.7.

It seems that you are not linking to the right python. I don’t know why this is, but when I call source activate foo I usually see:

Maybe @asmeurer has some ideas

I don’t use bash, so I don’t use activate. I had to hack my own solution
together.

But why does pip work in Python 3 but not 2?

On Tuesday, July 22, 2014, Andy R. Terrel notifications@github.com wrote:

It seems that you are not linking to the right python. I don’t know why
this is, but when I call source activate foo I usually see:

discarding from PATH
prepending to PATH

—
Reply to this email directly or view it on GitHub
#823 (comment).

More info: I use the fish shell.

This has only started happening recently and I can’t think of a change that
would cause it. I guess I can blow away my miniconda install and start
over, see if that helps.

On Tuesday, July 22, 2014, Andy R. Terrel notifications@github.com wrote:

It seems that you are not linking to the right python. I don’t know why
this is, but when I call source activate foo I usually see:

discarding from PATH
prepending to PATH

—
Reply to this email directly or view it on GitHub
#823 (comment).

Okay looks like fish isn’t the problem.

> set -x PATH /Users/aterrel/workspace/apps/anaconda/miniconda-3.5.5-py34/envs/py27/bin/ $PATH aterrel@tulip

> python Python 2.7.8 |Continuum Analytics, Inc.| (default, Jul 2 2014, 15:36:00) [GCC 4.2.1 (Apple Inc. build 5577)] on darwin Type «help», «copyright», «credits» or «license» for more information. Anaconda is brought to you by Continuum Analytics. Please check out: http://continuum.io/thanks and https://binstar.org >>> import setuptools >>> aterrel@tulip

> ls (dirname (which python))/../lib/python2.7/site-packages README setuptools-3.6-py2.7.egg setuptools.pth «>

My setup looks the same:

Like I said, it used to work fine and then it stopped. If I bootstrap install pip ( wget https://bootstrap.pypa.io/get-pip.py -O — | python ) things continue to work fine.

I guess we can chalk this up to some oddity of my system, I’ll let you know if I ever find out what’s going on.

Can you show conda info -a ?

You can see that it is installing setuptools when it installs pip.

This is the output of conda info -a when I’m in the py27 environment that demonstrates this problem:

Out of curiosity, is there a reason conda uses setuptools 3.6 instead of the most recent 5.4.1?

I guess we haven’t updated it in a while. @ilanschnell

Try conda install -f setuptools in that environment.

Is there a place we can contribute updated recipes for core conda use the way you can with Homebrew? E.g. pytest is out of date too, but I hate pestering you all every time this happens. Is that what conda/conda-recipes is for?

At this point, no, we use a separate internal repo for the recipes for our official packages.

I ran conda install -f setuptools and now pip works even after I destroy an environment and recreate it. (I accidentally ran conda install -f setuptools in my root environment too, dunno if that could be having an influence somehow.) Weirdness.

Conda works by unpacking the packages in the pkgs directory and then hard linking them to the environment. Sometimes these get corrupted somehow, breaking all environments that use them, and also any additional environments, since the same files are hard linked each time. conda install -f unarchives the package again. Note that this breaks the links to any other environments that already had setuptools installed, so you’ll have to reinstall it there too (it also means that running conda install -f a lot can use up a lot of disk space if you have a lot of environments).

Doing so in your root environment wouldn’t affect it because the Python 3 version of setuptools is a separate package. An even if it were the same package it wouldn’t because it would just break the link.

Ah, thanks for the explanation.

That’s one for an FAQ.
On Jul 28, 2014 5:07 PM, «Aaron Meurer» notifications@github.com wrote:

Conda works by unpacking the packages in the pkgs directory and then hard
linking them to the environment. Sometimes these get corrupted somehow,
breaking all environments that use them, and also any additional
environments, since the same files are hard linked each time. conda
install -f unarchives the package again. Note that this breaks the links
to any other environments that already had setuptools installed, so you’ll
have to reinstall it there too (it also means that running conda install -f
a lot can use up a lot of disk space if you have a lot of environments).

Doing so in your root environment wouldn’t affect it because the Python 3
version of setuptools is a separate package. An even if it were the same
package it wouldn’t because it would just break the link.

—
Reply to this email directly or view it on GitHub
#823 (comment).

Источник

Current Behavior

Running conda install pip in an environment produces an error

CondaFileIOError: '/anaconda3/pkgs/pip-19.0.3-py37_0.tar.bz2'. contains unsafe path: bin/pip

Steps to Reproduce

~ $ conda create -n myenv pip
Collecting package metadata: done
Solving environment: done

## Package Plan ##

  environment location: /anaconda3/envs/myenv

  added / updated specs:
    - pip


The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    pip-19.0.3                 |           py37_0         1.8 MB
    ------------------------------------------------------------
                                           Total:         1.8 MB

The following NEW packages will be INSTALLED:

  ca-certificates    pkgs/main/osx-64::ca-certificates-2019.1.23-0
  certifi            pkgs/main/osx-64::certifi-2019.3.9-py37_0
  libcxx             pkgs/main/osx-64::libcxx-4.0.1-hcfea43d_1
  libcxxabi          pkgs/main/osx-64::libcxxabi-4.0.1-hcfea43d_1
  libedit            pkgs/main/osx-64::libedit-3.1.20181209-hb402a30_0
  libffi             pkgs/main/osx-64::libffi-3.2.1-h475c297_4
  ncurses            pkgs/main/osx-64::ncurses-6.1-h0a44026_1
  openssl            pkgs/main/osx-64::openssl-1.1.1b-h1de35cc_1
  pip                pkgs/main/osx-64::pip-19.0.3-py37_0
  python             pkgs/main/osx-64::python-3.7.2-haf84260_0
  readline           pkgs/main/osx-64::readline-7.0-h1de35cc_5
  setuptools         pkgs/main/osx-64::setuptools-40.8.0-py37_0
  sqlite             pkgs/main/osx-64::sqlite-3.27.2-ha441bb4_0
  tk                 pkgs/main/osx-64::tk-8.6.8-ha441bb4_0
  wheel              pkgs/main/osx-64::wheel-0.33.1-py37_0
  xz                 pkgs/main/osx-64::xz-5.2.4-h1de35cc_4
  zlib               pkgs/main/osx-64::zlib-1.2.11-h1de35cc_3


Proceed ([y]/n)? y


Downloading and Extracting Packages
pip-19.0.3           | 1.8 MB    | ######################################################## | 100%

CondaFileIOError: '/anaconda3/pkgs/pip-19.0.3-py37_0.tar.bz2'. contains unsafe path: bin/pip

Expected Behavior

Pip installs successfully.

Environment Information

`conda info`

     active environment : tftest
    active env location : /anaconda3/envs/tftest
            shell level : 2
       user config file : /Users/malmaud/.condarc
 populated config files : /Users/malmaud/.condarc
          conda version : 4.6.8
    conda-build version : 3.17.6
         python version : 3.7.1.final.0
       base environment : /anaconda3  (writable)
           channel URLs : https://repo.anaconda.com/pkgs/main/osx-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/osx-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/osx-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /anaconda3/pkgs
                          /Users/malmaud/.conda/pkgs
       envs directories : /anaconda3/envs
                          /Users/malmaud/.conda/envs
               platform : osx-64
             user-agent : conda/4.6.8 requests/2.21.0 CPython/3.7.1 Darwin/18.2.0 OSX/10.14.3
                UID:GID : 501:20
             netrc file : None
           offline mode : False

`conda config --show-sources`

==> /Users/malmaud/.condarc <==
changeps1: False

`conda list --show-channel-urls`

# packages in environment at /anaconda3/envs/tftest:
#
# Name                    Version                   Build  Channel

I am getting a new error on Jupyter Lab I have not encountered when installing Python packages before:

>>>!pip install fuzzywuzzy ###This used to work perfectly until two days ago.

Defaulting to user installation because normal site-packages is not writeable
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fa55f3217d0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/fuzzywuzzy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fa55f321bd0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/fuzzywuzzy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fa55f321f10>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/fuzzywuzzy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fa55f336290>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/fuzzywuzzy/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fa55f3365d0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/fuzzywuzzy/
ERROR: Could not find a version that satisfies the requirement fuzzywuzzy (from versions: none)
ERROR: No matching distribution found for fuzzywuzzy

(Same error for ANY package)

This is what I have tried:

>>> conda install -c conda-forge fuzzywuzzy

Collecting package metadata (current_repodata.json): failed

CondaHTTPError: HTTP 000 CONNECTION FAILED for url <https://conda.anaconda.org/conda-forge/linux-64/current_repodata.json>
Elapsed: -

An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.
'https://conda.anaconda.org/conda-forge/linux-64'



Note: you may need to restart the kernel to use updated packages.

>>>pip3 install fuzzywuzzy ###in terminal

>>>python -m pip install fuzzywuzzy ###in terminal

The pip version seems to be up to date

python -m pip --version
pip 21.1.1 from /glob/development-tools/versions/oneapi/2021.3/inteloneapi/intelpython/latest/lib/python3.7/site-packages/pip (python 3.7)

And cannot install pip again or create a conda environment:

uxxxxx@s001-n002:~$ curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0curl: (6) Could not resolve host: bootstrap.pypa.io

Next steps?

При установке абсолютно любой библиотеки pip возникает ошибка, побывал на многих форумах но ответа так и не нашёл, может здесь помогут. Вот сама ошибка:

pip install pyAudio
Defaulting to user installation because normal site-packages is not writeable
Collecting PyAudio
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, ConnectionResetError(104, ‘Соединение разорвано другой стороной’))’: /packages/ab/42/b4f04721c5c5bfc196ce156b3c768998ef8c0ae3654ed29ea5020c749a6b/PyAudio-0.2.11.tar.gz
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, ConnectionResetError(104, ‘Соединение разорвано другой стороной’))’: /packages/ab/42/b4f04721c5c5bfc196ce156b3c768998ef8c0ae3654ed29ea5020c749a6b/PyAudio-0.2.11.tar.gz
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, ConnectionResetError(104, ‘Соединение разорвано другой стороной’))’: /packages/ab/42/b4f04721c5c5bfc196ce156b3c768998ef8c0ae3654ed29ea5020c749a6b/PyAudio-0.2.11.tar.gz
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, ConnectionResetError(104, ‘Соединение разорвано другой стороной’))’: /packages/ab/42/b4f04721c5c5bfc196ce156b3c768998ef8c0ae3654ed29ea5020c749a6b/PyAudio-0.2.11.tar.gz
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, ConnectionResetError(104, ‘Соединение разорвано другой стороной’))’: /packages/ab/42/b4f04721c5c5bfc196ce156b3c768998ef8c0ae3654ed29ea5020c749a6b/PyAudio-0.2.11.tar.gz
ERROR: Could not install packages due to an EnvironmentError: HTTPSConnectionPool(host=’files.pythonhosted.org’, port=443): Max retries exceeded with url: /packages/ab/42/b4f04721c5c5bfc196ce156b3c768998ef8c0ae3654ed29ea5020c749a6b/PyAudio-0.2.11.tar.gz (Caused by ProtocolError(‘Connection aborted.’, ConnectionResetError(104, ‘Соединение разорвано другой стороной’)))