Skip to content

Conversation

@wyattscarpenter
Copy link
Contributor

@wyattscarpenter wyattscarpenter commented Nov 8, 2025

As I was adapting the mypy codebase to include some new stubs, I realized that the requirements.txt files tell you to run pip-compile --output-file=test-requirements.txt --strip-extras --allow-unsafe test-requirements.in, and thus have an implicit undeclared requirement on pip-tools. I tried adding this to build-requirements.txt but that broke some things so I put it in a new extra dependency group called dev instead.

A specific version floor is required due to very broken behavior on an earlier version of pip-tools. As is the version ceiling on pip because, wouldn't you know it, a later version of pip broke compatibility with pip-tools again. (I discovered that by manual testing, and my manual testing tells me this change apparently works fine; I can install the extra and then run the command with uv run (an isolated environment).)

…e some new stubs, I realized that the requirements.txt files tell you to run pip-compile --output-file=test-requirements.txt --strip-extras --allow-unsafe test-requirements.in, and thus have an implicit undeclared requirement on pip-tools. I tried adding this to build-requirements.txt but that broke some things so I put it in a new extra called dev instead.
@github-actions

This comment has been minimized.

@wyattscarpenter wyattscarpenter changed the title Add a new extra called dev and add pip-tools to it. Add a new dependency group called dev and add pip-tools to it. Nov 8, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 8, 2025

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants