[ python-Bugs-1162912 ] typesseq-mutable lacks note on combined key/cmp usage
SourceForge.net
noreply at sourceforge.net
Sun Jul 3 22:22:27 CEST 2005
Bugs item #1162912, was opened at 2005-03-14 12:20
Message generated for change (Comment added) made by birkenfeld
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1162912&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: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Stefan Behnel (scoder)
>Assigned to: Reinhold Birkenfeld (birkenfeld)
Summary: typesseq-mutable lacks note on combined key/cmp usage
Initial Comment:
The documentation about list.sort() and sorted() does
not state how the keyword arguments cmp and key
interact. Aparently, if key is supplied, cmp works on
the result of the key function and no longer on the
item itself. This should be documented.
----------------------------------------------------------------------
>Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-07-03 22:22
Message:
Logged In: YES
user_id=1188172
Thanks for the report and the patch.
Committed as Doc/lib/libstdtypes.tex r1.183, r1.170.2.12.
----------------------------------------------------------------------
Comment By: Peter van Kampen (pterk)
Date: 2005-07-03 22:00
Message:
Logged In: YES
user_id=174455
I have submittted a doc patch (#1231890) that adds a note
that reads:
If both key and cmp are supplied the key function is
applied before the cmp function.
(You can check listsort in listobject.c to verify)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1162912&group_id=5470
More information about the Python-bugs-list
mailing list