Skip to content

Navigation Menu

Explore
By size
By industry
By use case
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

python / peps Public

Notifications You must be signed in to change notification settings
Fork 1.5k
Star 4.4k

Code
Issues 19
Pull requests 31
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Back to pull request #3845

PEP 667: Clarify specification ambiguities and the expected impact #7030

Sign in to view logs

Sign in to view logs

PEP 667: Clarify specification ambiguities and the expected impact

PEP 667: Clarify specification ambiguities and the expected impact #7030

Summary
Jobs
- Run pre-commit
- Run check-peps
Run details
- Usage
- Workflow file

Usage Workflow file

Run check-peps

succeeded Sep 4, 2024 in 4s

Loading

Re-running jobs...

You can’t perform that action at this time.