This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2012年08月10日 17:00 by anton.barkovsky, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| set_pop_doc.patch | anton.barkovsky, 2012年08月10日 17:00 | Clarify set.pop() documentation | review | |
| Messages (4) | |||
|---|---|---|---|
| msg167895 - (view) | Author: Anton Barkovsky (anton.barkovsky) * | Date: 2012年08月10日 17:00 | |
I've seen people being confused by the documentation for set.pop() method. It makes it look like the element is selected randomly while it's just unspecified. I'm attaching a patch that clarifies the doc, tested on 3.3, 3.2 and 2.7 |
|||
| msg167896 - (view) | Author: Georg Brandl (georg.brandl) * (Python committer) | Date: 2012年08月10日 17:14 | |
Sorry, I don't see how "arbitrary" implies "random". So I'm -1 on making the docs more verbose for no apparent gain. |
|||
| msg167898 - (view) | Author: Eli Bendersky (eli.bendersky) * (Python committer) | Date: 2012年08月10日 17:40 | |
I agree with Georg. As far as I understand the word "arbitrary" - it describes the situation exactly. |
|||
| msg168022 - (view) | Author: Raymond Hettinger (rhettinger) * (Python committer) | Date: 2012年08月12日 05:17 | |
I concur with Georg and Eli. The word "arbitrary" was chosen intentionally. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:34 | admin | set | github: 59824 |
| 2012年08月12日 05:17:46 | rhettinger | set | nosy:
+ rhettinger messages: + msg168022 |
| 2012年08月10日 18:32:34 | georg.brandl | set | status: open -> closed resolution: works for me |
| 2012年08月10日 17:40:15 | eli.bendersky | set | nosy:
+ eli.bendersky messages: + msg167898 |
| 2012年08月10日 17:14:18 | georg.brandl | set | nosy:
+ georg.brandl messages: + msg167896 |
| 2012年08月10日 17:00:36 | anton.barkovsky | create | |