-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-33602: Remove set and queue references from Data Types #7055
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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.
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"
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 |
@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? |
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. |
Thanks for making the requested changes! @rhettinger, @serhiy-storchaka: please review the changes made to this pull request. |
@rhettinger any chance you could give a look at the changes made and my comments? |
@rhettinger could you take a look at the changes I made after your comments? Please note the comment I left in #7055 (review) |
@rhettinger Do you approve of the changes made on the commits following your request? |
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 |
@rhettinger could you take a look at this? |
@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? |
Has been resolved by the author.
(closing and re-opening to restart CI, Azure was stuck) |
Thanks @andresdelfino for the PR, and @JulienPalard for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
…onGH-7055) (cherry picked from commit 9121088) Co-authored-by: Andre Delfino <[email protected]>
GH-15875 is a backport of this pull request to the 3.8 branch. |
…onGH-7055) (cherry picked from commit 9121088) Co-authored-by: Andre Delfino <[email protected]>
GH-15876 is a backport of this pull request to the 3.7 branch. |
) (GH-15875) (cherry picked from commit 9121088) Co-authored-by: Andre Delfino <[email protected]>
) (GH-15876) (cherry picked from commit 9121088) Co-authored-by: Andre Delfino <[email protected]>
@andresdelfino thanks! |
https://bugs.python.org/issue33602