| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Do we foresee any other uses for such a utility function? If not, I'd prefer just a direct check in test_gdb. |
Sorry, something went wrong.
I thought it might be helpful in the future. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
|
Ok then. I updated my PR. Thanks a lot for your help. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
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!
Sorry, something went wrong.
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.
Sorry, something went wrong.
There was a problem hiding this comment.
No need for the comma (,) there.
Sorry, something went wrong.
|
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 I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
I have made the requested changes; please review again I have added a news entry, but I am not exactly sure about the wording. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @ned-deily: please review the changes made to this pull request. |
Sorry, something went wrong.
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 ....
Sorry, something went wrong.
|
Can I directly change the NEWS entry or should I somehow use blurb to do so? |
Sorry, something went wrong.
|
Either way is fine. |
Sorry, something went wrong.
|
I just committed one last time to update Misc/ACKS and the news entry. Thanks a lot for the review and all your help. |
Sorry, something went wrong.
|
Thanks @lysnikolaou for the PR, and @ned-deily for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
Sorry, something went wrong.
|
GH-10325 is a backport of this pull request to the 3.7 branch. |
Sorry, something went wrong.
pythonGH-10318) (cherry picked from commit 59668aa) Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
|
Thanks @lysnikolaou for the PR, and @ned-deily for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6. |
Sorry, something went wrong.
|
GH-10326 is a backport of this pull request to the 3.6 branch. |
Sorry, something went wrong.
pythonGH-10318) (cherry picked from commit 59668aa) Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
| Back | FazBrowse Home | New Git URL |
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