Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-134585: disable_Atomic
and__thread
keywords during CLion parsing phase#134625
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
bedevere-bot commentedMay 24, 2025
🤖 New build scheduled with the buildbot fleet by@picnixz for commit880cfce 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F134625%2Fmerge If you want to schedule another build, you need to add the🔨 test-with-buildbots label again. |
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I hate this hack, but if there is no other way, then... well.
Wait a little longer before merge in case someone comes up with a better idea.
Me too. I hate it and I would have helped CLion's team to come up with a fix but since it's not part of the opensource projects I can only wait for them to do something about it...
I can definitely wait. I've been working on CPython for the past 10 months with that and so if someone has a better idea, I'll be really happy to use it. |
Found a (possible) workaround by using clang:#134585 (comment). |
Uh oh!
There was an error while loading.Please reload this page.
_Atomic
and__thread
keywords on JetBrains IDE only #134585