Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.4k
gh-105858: Expose some union-related objects as internal APIs#116025
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
We now use these in the AST parsing code afterpythongh-105880. A few comparable types (e.g.,NoneType) are already exposed as internal APIs.
This should fix these buildbot failures:#105880 (comment) I tested locally by running |
bedevere-bot commentedFeb 28, 2024
🤖 New build scheduled with the buildbot fleet by@JelleZijlstra for commit5142722 🤖 If you want to schedule another build, you need to add the🔨 test-with-buildbots label again. |
The macOS builds are failing with something related to 2to3 that doesn't seem due to my changes: |
…ythonGH-116025)We now use these in the AST parsing code afterpythongh-105880. A few comparable types (e.g.,NoneType) are already exposed as internal APIs.
…ythonGH-116025)We now use these in the AST parsing code afterpythongh-105880. A few comparable types (e.g.,NoneType) are already exposed as internal APIs.
…ythonGH-116025)We now use these in the AST parsing code afterpythongh-105880. A few comparable types (e.g.,NoneType) are already exposed as internal APIs.
Uh oh!
There was an error while loading.Please reload this page.
We now use these in the AST parsing code aftergh-105880. A few comparable types (e.g.,
NoneType) are already exposed as internal APIs.