Uh oh!
There was an error while loading. Please reload this page.
bpo-21263: Skip test_gdb when python has been compiled with LLVM clang - #10318
Conversation
ned-deily
commented
Nov 4, 2018
Do we foresee any other uses for such a utility function? If not, I'd prefer just a direct check in test_gdb. |
I thought it might be helpful in the future. |
ned-deily
commented
Nov 4, 2018
Importing again is fine. That's the way Python works! While it is often a good idea to not repeat yourself, in this case the test is so simple that it is almost more work to create and document a utility function. I would leave it out. |
lysnikolaou
commented
Nov 4, 2018
Ok then. I updated my PR. Thanks a lot for your help. |
lysnikolaou
commented
Nov 4, 2018
Should I maybe include a news entry for this? I have never done so in the past, but I am not sure about this PR. |
ned-deily
left a comment
There was a problem hiding this comment.
With regard to a NEWS entry, since there are already two bpo issues that have been opened about this, I suppose it makes sense to include one. If you feel comfortable doing so, you can use the blurb tool to do so. Otherwise, the core committer making the final merge could do it. Thanks!
There was a problem hiding this comment.
Sorry, I didn't notice this before but the skip should be limited to macOS, i.e. add a sys.platform == "darwin" clause to the if test. AFAICT gdb does work OK with clang on Linux for example.
bedevere-bot
commented
Nov 4, 2018
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
lysnikolaou
commented
Nov 4, 2018
I have made the requested changes; please review again I have added a news entry, but I am not exactly sure about the wording. |
bedevere-bot
commented
Nov 4, 2018
Thanks for making the requested changes! @ned-deily: please review the changes made to this pull request. |
ned-deily
left a comment
There was a problem hiding this comment.
Looks good, thanks! If you like, you can add your name to Misc/ACKS and to the NEWS entry: Patch by ....
Can I directly change the NEWS entry or should I somehow use |
ned-deily
commented
Nov 4, 2018
Either way is fine. |
lysnikolaou
commented
Nov 4, 2018
I just committed one last time to update |
miss-islington
commented
Nov 4, 2018
Thanks @lysnikolaou for the PR, and @ned-deily for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
bedevere-bot
commented
Nov 4, 2018
GH-10325 is a backport of this pull request to the 3.7 branch. |
pythonGH-10318) (cherry picked from commit 59668aa) Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
miss-islington
commented
Nov 4, 2018
Thanks @lysnikolaou for the PR, and @ned-deily for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6. |
bedevere-bot
commented
Nov 4, 2018
GH-10326 is a backport of this pull request to the 3.6 branch. |
pythonGH-10318) (cherry picked from commit 59668aa) Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
I have also added a new field in the test support module, which enables one to find out which compiler was used to build Python.
https://bugs.python.org/issue21263