Repository navigation
Conversation
Claim of being *the* replacement for requirements.txt is also a bit nonsensical.
Too niche to list here as a packaging project, it's a single nginx.conf file.
rgommers
added
the
type: maintenance
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is only a first cut, removing unmaintained, very outdated, or irrelevant entries, as part of gh-2170.
There's more to do to bring this page up-to-date, but that's for a follow-up PR after discussion on what the scope of this page should be going forward. These removals should all be uncontroversial. One commit per removed entry, with reason in the commit message. (fine to squash-merge if preferred, just for review one commit per entry is easier)
📚 Documentation preview 📚: https://python-packaging-user-guide--2179.org.readthedocs.build/en/2179/