[ python-Bugs-1429053 ] set documentation deficiencies
SourceForge.net
noreply at sourceforge.net
Sat Jul 29 19:27:05 CEST 2006
Bugs item #1429053, was opened at 2006-02-10 07:07
Message generated for change (Comment added) made by akuchling
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429053&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Keith Briggs (kbriggs)
>Assigned to: A.M. Kuchling (akuchling)
Summary: set documentation deficiencies
Initial Comment:
http://www.python.org/doc/current/lib/types-set.html
has a dead link: "Module sets".
Also, there does not seem to be any documentation on
how to construct a set. Does set()==set([])? What
is allowed as an argument to set()? Any iterable?
----------------------------------------------------------------------
>Comment By: A.M. Kuchling (akuchling)
Date: 2006-07-29 13:27
Message:
Logged In: YES
user_id=11375
This bug seems to be fixed; closing.
----------------------------------------------------------------------
Comment By: Georg Brandl (birkenfeld)
Date: 2006-02-13 14:29
Message:
Logged In: YES
user_id=1188172
The new location of the devel docs is
http://docs.python.org/dev.
----------------------------------------------------------------------
Comment By: Keith Briggs (kbriggs)
Date: 2006-02-13 07:12
Message:
Logged In: YES
user_id=888261
Where is it fixed? I see all the same problems at
http://www.python.org/dev/doc/devel/lib/types-set.html.
----------------------------------------------------------------------
Comment By: Georg Brandl (birkenfeld)
Date: 2006-02-10 11:21
Message:
Logged In: YES
user_id=1188172
This is all already corrected, except for the empty set thing.
----------------------------------------------------------------------
Comment By: Keith Briggs (kbriggs)
Date: 2006-02-10 10:53
Message:
Logged In: YES
user_id=888261
Furthermore, the operations update etc. are mutations of s,
so wouldn't the definitions
s.update(t) s |= t return set s with elements added from t
s.intersection_update(t) s &= t return set s keeping only
elements also found in t
s.difference_update(t) s -= t return set s after removing
elements found in t
s.symmetric_difference_update(t) s ^= t return set s with
elements from s or t but not both
be better as
s.update(t) s |= t add elements from t to s
etc.?
I'm not sure what the word "return" is doing here.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429053&group_id=5470
More information about the Python-bugs-list
mailing list