[SERVER-53250] Evaluate consequences of using upgraded pip in virtual environment and pip's new dependency resolver Created: 05/Dec/20  Updated: 29/Oct/23  Resolved: 26/Mar/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.4.3, 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-53579 python's dev-requirements.txt is inco... Closed
is related to SERVER-49504 Allow resmoke's mongo shell to log to... Closed
is related to SERVER-55527 Investigate use of --system-site-pack... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.9, v4.4
Sprint: STM 2020-12-14, STM 2021-04-05
Participants:
Linked BF Score: 0
Story Points: 3

 Description   

The 4.2, 4.4, and master branches all use python -m venv and not python -m virtualenv to create the virtual environment. The venv package comes with Python3.

This leads to pip 10.0.1 from Python 3.7.0's ensurepip to be used to download Python packages on the 4.2 and 4.4 branches. The changes from 3c179e4 as part of SERVER-49504 cause pip 10.0.1 to be upgraded to the latest version (20.3.1 as of today). Versions of pip 20.3 and newer use a new dependency resolver by default.

# /opt/mongodbtoolchain/v3/bin/python3 -m ensurepip --version
pip 10.0.1



 Comments   
Comment by Githook User [ 25/Mar/21 ]

Author:

{'name': 'Robert Guo', 'email': 'guo@Roberts-MacBook-Pro.local'}

Message: SERVER-53250 use new pip resolver
Branch: master
https://github.com/mongodb/mongo/commit/6afd283045dc43c0b249424ba03a72b89e5ad8c6

Comment by Githook User [ 10/Dec/20 ]

Author:

{'name': 'Richard Samuels', 'email': 'richard.l.samuels@gmail.com', 'username': 'richardsamuels'}

Message: SERVER-53250 use pip legacy resolver to fix pip hangs on static builders

(cherry picked from commit 4ba4acbe4a16e18af4b59eed59686902806b8f49)
Branch: v4.4
https://github.com/mongodb/mongo/commit/719e81b31715239248e786fa1545ad6e30099b54

Comment by Githook User [ 09/Dec/20 ]

Author:

{'name': 'Richard Samuels', 'email': 'richard.l.samuels@gmail.com', 'username': 'richardsamuels'}

Message: SERVER-53250 use pip legacy resolver to fix pip hangs on static builders
Branch: master
https://github.com/mongodb/mongo/commit/4ba4acbe4a16e18af4b59eed59686902806b8f49

Comment by Brian Samek [ 07/Dec/20 ]

zakhar.kleyman - I worry that exempting some hosts could hide a problem on AWS hosts. If what's happening is that downloads are so slow on non-AWS hosts that the tasks time out, it could be that downloads on AWS hosts are significantly slower than before, slowing all tasks down, but not enough to cause purple.

Generated at Thu Feb 08 05:30:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.