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 / pip Public

Notifications You must be signed in to change notification settings
Fork 3k
Star 9.6k

Code
Issues 972
Pull requests 139
Actions
Projects 1
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

fix: correct the way to decide if keyring is available#11774

Merged

pradyunsg merged 3 commits intopypa:mainpypa/pip:mainfrom frostming:fix/keyringfrostming/pip:fix/keyringCopy head branch name to clipboard

Feb 3, 2023

+11-4

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Feb 3, 2023

fix: correct the way to decide if keyring is available
frostming
committed
add news
frostming
committed
use a attribute to tell if the provider is null
frostming
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.