Mailing List Archive: Python: Bugs

[issue15619] set.pop() documentation is confusing

Index | Next | Previous | View Threaded

report at bugs

Aug 10, 2012, 10:00 AM

Post #1 of 5 (94 views)
Permalink

[issue15619] set.pop() documentation is confusing

New submission from Anton Barkovsky:

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

----------
assignee: docs [at] pytho
components: Documentation
files: set_pop_doc.patch
keywords: patch
messages: 167895
nosy: anton.barkovsky, docs [at] pytho
priority: normal
severity: normal
status: open
title: set.pop() documentation is confusing
versions: Python 2.7, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file26759/set_pop_doc.patch

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue15619>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

report at bugs

Aug 10, 2012, 10:14 AM

Post #2 of 5 (87 views)
Permalink

[issue15619] set.pop() documentation is confusing [In reply to]

Georg Brandl added the comment:

Sorry, I don't see how "arbitrary" implies "random". So I'm -1 on making the docs more verbose for no apparent gain.

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue15619>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

report at bugs

Aug 10, 2012, 10:40 AM

Post #3 of 5 (85 views)
Permalink

[issue15619] set.pop() documentation is confusing [In reply to]

Eli Bendersky added the comment:

I agree with Georg. As far as I understand the word "arbitrary" - it describes the situation exactly.

----------
nosy: +eli.bendersky

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue15619>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

report at bugs

Aug 10, 2012, 11:32 AM

Post #4 of 5 (85 views)
Permalink

[issue15619] set.pop() documentation is confusing [In reply to]

Changes by Georg Brandl <georg [at] python>:

----------
resolution: -> works for me
status: open -> closed

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue15619>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

report at bugs

Aug 11, 2012, 10:17 PM

Post #5 of 5 (82 views)
Permalink

[issue15619] set.pop() documentation is confusing [In reply to]

Raymond Hettinger added the comment:

I concur with Georg and Eli. The word "arbitrary" was chosen intentionally.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue15619>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads