[SERVER-71268] Simplify Python requirement files Created: 10/Nov/22 Updated: 27/Oct/23 Resolved: 08/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ryan Egesdahl (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||
| Participants: | |||||||||
| Description |
|
We currently have multiple Python requirement files, each suited for different purposes. It's become difficult over time to determine which requirements file in which to place a new module requirement, especially since we don't always know which requirements a consumer might use. We only have at most two different types of consumers (developers/CI and production) for these files, so we should consolidate the requirements files as much as possible to reduce our support footprint. |
| Comments |
| Comment by Alex Neben [ 08/Sep/23 ] |
|
Using poetry now! Whooohooo! |
| Comment by Ryan Egesdahl (Inactive) [ 03/Jan/23 ] |
|
alexander.neben@mongodb.com I agree, if it's possible. pipx only supports things used strictly as commands, though. Anything used as a library has to be in the venv. |
| Comment by Alex Neben [ 03/Jan/23 ] |
|
I think we should go bigger than just unifying our dependencies. We should use a tool like pipx and just try to get rid of depdencies. |