[SERVER-56189] pywin32 pip module should be installed no-binary Created: 20/Apr/21 Updated: 19/Jun/23 Resolved: 19/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ryan Egesdahl (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sdp-backlog-purge | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Operating System: | ALL |
| Participants: |
| Description |
|
The {{ {pywin32}}} module has an associated post-install script that has to be run after installation. Not running the script leads to errors that look like this when attempting to run {{ {resmoke.py}}} on Windows:
When the module is installed as a {{ {wheel}}}, the post-install script does not run, leading to the confusing error above. We should consider adding {--no-binary=pywin32} as an argument to the module in {{ {requirements.txt}}}. Until this is done, users on Windows can run the script manually, as documented here: |
| Comments |
| Comment by Alex Neben [ 19/Jun/23 ] |
|
This has been identified as work that the SDP team won't do in the near term. Please reopen with a comment if you feel this work should be reprioritized and explain why. |