Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

pypa / packaging Public

Notifications You must be signed in to change notification settings
Fork 252
Star 632

Code
Issues 84
Pull requests 21
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Correctly handle non-normalised specifiers in requirements#634

Merged

pradyunsg merged 3 commits intopypa:mainpypa/packaging:mainfrom pradyunsg:fix-requirements-specifierpradyunsg/packaging:fix-requirements-specifierCopy head branch name to clipboard

Dec 8, 2022

+12-16

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Dec 8, 2022

Use regular expression from specifiers as-is for requirement parsing
pradyunsg
committed
Reorder specifier matching to try longer names first
pradyunsg
committed
Add a test case for non-normalised specifiers
pradyunsg
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.