b132ca0980
Upgrading pip3 after pip2 caused the pip command to be aliased to the pip3 command. However, since we are still transitioning from Python 2 to Python 3, most pip commands in the codebase are expecting pip to alias to pip2. The proper solution here is to explicitly call pip2 and pip3, and no longer call pip, however this will require extensive changes and testing, so to quickly fix this issue, we upgraded pip2 after pip3 to ensure that pip2 is installed after pip3. |
||
|---|---|---|
| .. | ||
| Dockerfile.j2 | ||
| Dockerfile.user | ||
| no-check-valid-until | ||
| sonic-jenkins-id_rsa.pub | ||