Fix case sensitivity of entry point names and keys in setup.cfg. Fixes #1937 #2580
Conversation
This file contains 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
melissa-kun-li
changed the title
jaraco
approved these changes
Feb 24, 2021
jaraco
reviewed
Feb 24, 2021
|
Releasing as 53.1.0. Thanks again! |
Merged
2 tasks
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.
Summary of changes
Closes #1937
To address the bug of entry point names being made lower-case by Setuptools, this fix preserves case-sensitivity of keys in
setup.cfgby changingConfigParserto become case-sensitive. Edit: by extension this will also address any issues about keys insetup.cfgnot retaining case-sensitivity such as in #2480Pull Request Checklist
changelog.d/.(See documentation for details)