[SERVER-53789] Cap pip Dependencies Created: 14/Jan/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 4.0.22 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
Pymongo 4.0+ and pip 21+ will no longer support Python 2. We should cap those dependencies and cap others to a new-ish version to preempt similar events in the future. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |
| Comment by Brooke Miller [ 26/Jan/21 ] |
|
In triaging, robert.guo mentioned that this will need to be done for MDB 3.4 + and will be needed for both correctness and performance. Richard mentioned there are certain platforms (i.e. s390x) that will cause a lot of complexity here. |