bpo-33602: Remove set and queue references from Data Types#7055
Conversation
rhettinger
left a comment
There was a problem hiding this comment.
Please leave "heap queues" and "synchronized queues" as-is. They lose some of their meaning if you factor out the word "queue" which means something slightly different in each of the three cases.
Go ahead with removing "set" and adding "enumerations"
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.
|
@rhettinger I removed "synchronized queues" because they are now described in Concurrent Execution, and it seemed confusing to mention them if they are not listed below. I see your point about "heap" without "queue" attached to it, though. I can omit the mention to double-ended queues, so it reads "heap queues" again. Or perhaps "heap queues, double-ended queues, ...", but this sounded repetitive to me. Would that be ok for you? |
Sorry, something went wrong.
|
While I didn't literally made the requested changes, I'm pretty sure I addressed the issue raised and I think there was a confusion between "synchronized queues" and "double-ended queues", so: I have made the requested changes; please review again If I was wrong, I'll be glad to amend any error. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @rhettinger, @serhiy-storchaka: please review the changes made to this pull request. |
Sorry, something went wrong.
|
@rhettinger any chance you could give a look at the changes made and my comments? |
Sorry, something went wrong.
|
@rhettinger could you take a look at the changes I made after your comments? Please note the comment I left in #7055 (review) |
Sorry, something went wrong.
|
@rhettinger Do you approve of the changes made on the commits following your request? |
Sorry, something went wrong.
|
I removed the " needs backport to 3.6" label, the 3.6 branch no longer accept bugfixes (only security fixes are accepted): https://devguide.python.org/#status-of-python-branches |
Sorry, something went wrong.
|
@serhiy-storchaka could you -as the other reviewer of this PR- take a look on the changes made and see if they address the concerns Raymond shared? |
Sorry, something went wrong.
Has been resolved by the author.
|
(closing and re-opening to restart CI, Azure was stuck) |
Sorry, something went wrong.
|
Thanks @andresdelfino for the PR, and @JulienPalard for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
Sorry, something went wrong.
…onGH-7055) (cherry picked from commit 9121088) Co-authored-by: Andre Delfino <adelfino@gmail.com>
…onGH-7055) (cherry picked from commit 9121088) Co-authored-by: Andre Delfino <adelfino@gmail.com>
https://bugs.python.org/issue33602