[SERVER-40770] Remove etc/pip/constraints.txt and related infrastructure Created: 22/Apr/19  Updated: 29/Oct/23  Resolved: 13/May/19

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

Type: Task Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Mathew Robinson (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2019-05-20
Participants:

 Description   

constraints.txt was originally used to provide version-constrained pip project specification to the toolchain-builder/paranoid devs. Without the evergreen verify_pip task, it's best to remove this feature all together since it will likely not be refreshed often if at all. The steps involved in this:

  1. Rename etc/pip/toolchain-requirements.txt to etc/pip/complete-requirements.txt and include etc/pip/components/platform.req at the top. Use this file in etc/evergreen.yml.
  2. Switch toolchain-builder to use etc/pip/complete-requirements.txt instead of etc/pip/constraints.txt
  3. Remove etc/pip/constraints.txt and generate-pip-requirements.sh. Update etc/pip/README.md.


 Comments   
Comment by Githook User [ 13/May/19 ]

Author:

{'name': 'Mathew Robinson', 'username': 'chasinglogic', 'email': 'chasinglogic@gmail.com'}

Message: SERVER-40770 Remove etc/pip/constraints.txt and related infrastructure
Branch: master
https://github.com/mongodb/mongo/commit/18623882e47ecafa9b60509978b11342464d6956

Comment by Benjamin Caimano (Inactive) [ 23/Apr/19 ]

acm, I'm fine with that as long as we stage these changes reasonably.

Comment by Andrew Morrow (Inactive) [ 23/Apr/19 ]

ben.caimano - This is tangential to the actual change here, but I'd like to suggest a minor UX improvement. Could we please invert the names of the dependency files under etc/pip? Tab completing from etc/pip/r-<tab> to get a list of possible files would be far more useful than the current situation, where the "role" of the file comes first.

As a bridge, I'd propose that we make the renamed files canonical, and then make the old names forward to the new, for a release or two, then delete them.

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