bpo-39562: Prevent collision of future and compiler flags by isidentical · Pull Request #19230 · python/cpython · GitHub
GitHub CopilotWrite better code with AI | MCP RegistryIntegrate external tools | ActionsAutomate any workflow | CodespacesInstant dev environments | IssuesPlan and track work | Code ReviewManage code changes | Code QualityEnforce quality at merge | Why GitHub | Marketplace | View all features | Enterprises | Small and medium teams | Startups | View all use cases | View all industries | View all solutions | AI | Software Development | DevOps | Security | View all topics | Customer stories | Events & webinars | Ebooks & reports | Business insights | Trust center | Partners | View all resources
Tin mới
GitHub CopilotWrite better code with AI
GitHub Copilot appDirect agents from issue to merge
CodespacesInstant dev environments
Code ReviewManage code changes
Code QualityEnforce quality at merge
GitHub Advanced SecurityFind and fix vulnerabilities
Code securitySecure your code as you build
Secret protectionStop leaks before they start
GitHub SponsorsFund open source developers
Copilot for BusinessEnterprise-grade AI features
Premium SupportEnterprise-grade 24/7 support
Learn more about hiding disruptive comments
The reason will be displayed to describe this comment to others. Learn more.
bpo-39562: Prevent collision of future and compiler flags
Add support to compile for PyCF_ALLOW_TOP_LEVEL_AWAIT
Pack valid compile flags to a mask
automatically discover compiler flags from ast
Mention about change, describe tests, remove old macro
Apply suggestions Co-Authored-By: Victor Stinner <[email protected]>
Mention clashing variables, remove old comment
Add a noticement header, use dicts for tests
Merge branch 'master' into bpo-39562-2
bpo-40366: Remove support for passing obsolete flags into compile #19660
[3.8] bpo-39562: Prevent collision of future and compiler flags (
: Prevent collision of future and compiler flags (