Skip to content

Conversation

@moshemoshe137
Copy link

@moshemoshe137 moshemoshe137 commented Nov 23, 2025

Add dev-requirements.txt as a recognized filename for the existing "Pip requirements" language.

Description

dev-requirements.txt is commonly used in Python projects in addition to the existing requirements-dev.txt filename. A GitHub code search returns 5.7k repos using this filename, including python/pythondotorg, pintrest/snappass, dropbox/sqlalchemy-stubs, Patreon/patreon-python, meta-pytorch/torchsnapshot, and oracle/oci-mlflow to name a few.

There are multiple Python tools that recommend a filename of dev-requirements.txt, including:

  • pip-tools suggests creating a dev-requirements.txt for development dependencies. While not officially affiliated
    with pip, pip-tools has over 20 million downloads in the past month, according to online trackers.
  • pipenv migration guide recommends exporting to dev-requirements.txt:

    poetry export -f requirements.txt --dev --output dev-requirements.txt

  • deptry uses both dev-requirements.txt and requirements-dev.txt as default filenames for development dependencies.
  • Veracode's SCA uses both dev-requirements.txt and requirements-dev.txt as default filenames for pip_requirements_file.

Since linguist already recognizes requirements-dev.txt and requirements.lock.txt for Pip Requirements, adding dev-requirements.txt seems like a consistent addition that will improve highlighting for thousands of repos.

I didn't open a separate issue for this small change... I apologize if that's a faux pas 😅


@moshemoshe137 moshemoshe137 requested a review from a team as a code owner November 23, 2025 14:55
Copy link
Member

@lildude lildude left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a sample too. Please add a sample and update OP to use the template to state where the sample came from and its source. You will need to use the original template. In this case the extension section should do.

Add sample `dev-requirements.txt` from repo `gevent/gevent` (MIT License)
@moshemoshe137
Copy link
Author

Really sorry for messing up the PR template! I've added a sample file under the MIT license. I'm still learning, so I'm very grateful for your feedback and consideration 🙏 Please let me know if there is anything else I should adjust

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.

2 participants