Bug #10609
closedInstalling of Klever Python package with dependencies for openstack is broken with new versions of pip
0%
Description
pip warning:
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts. We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
Now in some cases installing Klever Python package can take enormous amount of time. pip starts looking at multiple versions of dependency its trying to install to determine which version is compatible with other requirements. As a result, pip downloads and tries every available version for each dependency, which is a very slow process.
pip suggests to provide the dependency resolver with stricter constraints to reduce runtime. We need to understand what is going on and fix the issue.
Updated by Evgeny Novikov over 3 years ago
Why not to use some version of PIP that was released before October 2020? For instance, our OpenStack instances and not only use pip==20.1 and they are happy. In addition, this version helps to avoid enormous delays when copying numerous auxiliary files like specifications, configurations and test cases. As far as I remember there was such the issues with newer versions of PIP as well.
Updated by Ilya Shchepetkov over 3 years ago
- Status changed from Open to Resolved
The issue is fixed in feature-10609 branch by adding additional requirements.txt file, that should be used when someone wants to deploy Klever to Openstack. I have checked that this works on my machine, but I suggest to test this branch more extensively before merging.
New dependency resolver reduces inconsistency (it will no longer install a combination of packages that is mutually inconsistent), so it doesn't make sense to continue using older versions of pip. I am sure that the bug you mentioned is already fixed.
Updated by Evgeny Novikov over 3 years ago
- Status changed from Resolved to Closed
Tests passed, though, in this case this does not mean that everything will be okay for everybody. Nevertheless, I merged the branch to master in 60a543b57. Everybody, please, take care about a slightly modified installation process, especially, for OpenStack. Do not rely on commands from the history.