[SERVER-62547] pip: Allow pywin32/pypiwin32 packages from the future Created: 12/Jan/22  Updated: 29/Oct/23  Resolved: 13/Jan/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Improvement Priority: Major - P3
Reporter: Billy Donahue Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-62480 Fix future_test files in MSVC 2022 un... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2022-1-24
Participants:

 Description   

Right now Python310 can't build on MSVC 2022 buildvariants because these modules are too new there. The == requirement is not necessary and can be relaxed into a >=.

Part of SERVER-62480 and broader MSVC2022 effort.



 Comments   
Comment by Robert Guo (Inactive) [ 13/Jan/22 ]

SGTM

Comment by Billy Donahue [ 13/Jan/22 ]

let's reopen if we need to discuss a max version

Comment by Billy Donahue [ 13/Jan/22 ]

CC: robert.guo
It was suggested in code review that a max version constraint should also be applied. Maybe we can discuss it, because I don't understand how it would help because we don't have any known problems with the current version of pywin32. Win32 is an API that's stable over decades, and pywin32 would be tracking it, so maybe putting upper bounds on module versions is more of a concern in other modules more than for pywin32?

Comment by Githook User [ 12/Jan/22 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-62547 enforce only a minimum pywin32 PIP module version
Branch: master
https://github.com/mongodb/mongo/commit/503acbbdd3e02fabb2fbc38c8e499df1d7559500

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