[SERVER-81072] Make venv when a spawnhost is created Created: 14/Sep/23 Updated: 23/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Trevor Guidry | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Correctness
|
| Participants: |
| Description |
|
A user was confused when they made a spawnhost and a venv was not there for them. It is trivial to make one in the start up script so we should just do that.
Original slack thread: https://mongodb.slack.com/archives/C0V79S1PY/p1694706450818099
|
| Comments |
| Comment by Trevor Guidry [ 20/Sep/23 ] |
|
I have never made a venv in windows but I imagine it can't be that hard. I could do linux implementation/testing in under an hour and windows probably could be done in the same hour. |
| Comment by Trevor Guidry [ 19/Sep/23 ] |
|
Well, it is already pretty easy to not use the venv and just use the system toolchain python. However adding a venv would make this more consistent with our normal workflow. |