packagefinder | Comfortable search for R packages | Build Tool library

From your current folder ., there is probably a file setup.py. In this file you have some extra options. One of them is full that probably contains the full dependencies for the current package.

So the command, try to install the package in the current folder and all its dependencies. full is just a convenient name, it doesn't mean nothing special for pip (or setup.py)

A better explanation is given here

Python packaging is "fun". Let's go on an adventure!

pip vendors urllib3, which automatically uses pyOpenSSL if it is present on Python < 2.7.9. This is done because Python < 2.7.9 does not support SNI in TLS; a critical modern feature. pyOpenSSL, in turn, depends on cryptography, which dropped 1.0.1 support in version 2.9. So when you attempt to do anything in pip it triggers an import sequence that results in this error.

The (likely) reason that you don't see this problem on another nearly identical server is that cryptography also ships binary wheels that statically link newer OpenSSLs. If you are on pip 8.x or better (which you likely were on the server that works and likely were not on the server that is broken) it will fetch a wheel linked against OpenSSL 1.1.1-latest (provided you're on x86_64. i686 wheels were dropped in 2.7).

Given the error message you're seeing you're almost certainly running cryptography 2.9.x on the broken server. That version supports an environment variable workaround. So if you do CRYPTOGRAPHY_ALLOW_OPENSSL_101=1 pip list it should work.

If that works then you should immediately upgrade cryptography. Since you're now running pip 20.x on this server the command CRYPTOGRAPHY_ALLOW_OPENSSL_101=1 pip install -U cryptography should install version 3.1 from a wheel (assuming you're running on x86_64).

If you are not running on x86_64 then you have two options (that don't involve upgrading your distribution, which you should since wheezy is long out of support!):

1. Always pass CRYPTOGRAPHY_ALLOW_OPENSSL_101 and never upgrade cryptography again (2.9.2 being the last version that even secretly supports 1.0.1)
2. Downgrade cryptography to 2.8 and also never upgrade it again.

This should serve as a tip and answer to your problem. I have worked with flask extensively and simple mess in your environment can mess your entire project and end up eating all your time while you are trying to get a fix online.If you encounter environment problem always recreate your project again. I would recommend you to work with Pycharm IDE because Anaconda environment can be mess up sometimes. follow the steps below to fix your issue

Fix 1

1. Open your anaconda prompt and Run this command on

python -m pip --version

1. After confirming the Pip Version and its location run an upgrade

python -m pip install --upgrade pip

1. To make sure everything is working fine run

conda update pip

Fix 2 Seems there is a problem with your packages

1. create a requirements.txt file in working directory
2. Automatically pass all your required packages to your requirements.txt by using the code below on python terminal

pip freeze > requirements.txt

1. Run the command below to install packages you might be missing or corrupted

pip install -r requirements.txt

All the best

The issue and the fix are described in read-the-docs issue #6554 (https://github.com/readthedocs/readthedocs.org/issues/6554):

Currently all builds are failing because the automatic upgrade (since #4823 ) to pip 20.0 was buggy (see pypa/pip#7620 ). There's now a 20.0.1 release which seems to have fixed the problem for others ... but how can I force my readthedocs to also upgrade to the .1 version?

The fix is to wipe out the build environment as follows (this is taken from https://docs.readthedocs.io/en/stable/guides/wipe-environment.html):

• Log in to read-the-docs
• Go to Versions
• Click on the Edit button of the version you want to wipe on the right side of the page
• Go to the bottom of the page and click the wipe link, next to the “Save” button
• Now you can re-build the version with a fresh build environment!

This fix worked for me (but as of 26-Jan-2020 you have to wipe out the environment for every build -- see comment from Grimmy below).