bpo-38880: List interpreters associated with a channel end#17323
bpo-38880: List interpreters associated with a channel end#17323miss-islington merged 34 commits into
Conversation
nanjekyejoannah
left a comment
There was a problem hiding this comment.
@LewisGaul it would be good to have a news entry. Use blurbit
Sorry, something went wrong.
ericsnowcurrently
left a comment
There was a problem hiding this comment.
Thanks so much for working on this. The approach you took looks good. I've left a lot of comments, but don't get disheartened. :) I'm just thorough. I didn't see any problems with correctness. My comments mostly fall into these groups:
- use
_PyInterpreterID_New() - the Python function signature can be simpler
- simplify the code:
- variable declarations should be where they are significant rather than at the top
- don't worry about optimization right now
- don't use goto where you don't need to
I'd be happy to discuss any of this further. Again, thanks for helping out!
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 |
Sorry, something went wrong.
I'm looking into this right now, and would be happy to work with you to get this finished over the weekend. I'll update you after I've had a look over the next few hours. |
Sorry, something went wrong.
@ericsnowcurrently I've replaced the implementation with the suggestion you had during the review and it seems to work better, with all tests now passing except |
Sorry, something went wrong.
|
Awesome. Let me know if I can help in any way. |
Sorry, something went wrong.
|
@ericsnowcurrently What seems to be happening is when I call |
Sorry, something went wrong.
|
I'd be glad to take a look with you. You open to a video chat? I'm available almost any time. |
Sorry, something went wrong.
|
btw, I added this change in #18817 and these tests are failing. This will block my next PR as I want to open a PR on using sub-interpreters for test suite . I want to know how to help as I believe @LewisGaul you have gone a long way into finishing this. |
Sorry, something went wrong.
|
@nanjekyejoannah I'm working on this - I have a call with Eric scheduled for Monday. The implementation is basically done, there's just an issue with one test case to do with closing a just one end of a channel. I'll let you know if any further help is required, thanks. |
Sorry, something went wrong.
|
@LewisGaul , nice thanks I will wait for the outcomes of your work with @ericsnowcurrently to open the new PR. Thanks |
Sorry, something went wrong.
|
@ericsnowcurrently Thanks for the chat earlier. I've updated the PR with a fix:
Should be good for re-review now! |
Sorry, something went wrong.
ericsnowcurrently
left a comment
There was a problem hiding this comment.
LGTM
Thanks for working on this! I only have one comment (a possible refleak). I'll merge the PR once that is addressed.
Sorry, something went wrong.
1 similar comment
|
Thanks @LewisGaul for your contribution. I really needed this ! |
Sorry, something went wrong.
|
Yay! |
Sorry, something went wrong.
This PR adds the functionality requested by ericsnowcurrently/multi-core-python#52.
https://bugs.python.org/issue38880
Automerge-Triggered-By: @ericsnowcurrently