[issue2761] Doc: built-in callables and map
Georg Brandl [EMAIL PROTECTED] added the comment: Problem is, we already have a section Builtin types. Fixed the map() docs in r62738, and added a note to the first sentence in r62739. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2761 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2761] Doc: built-in callables and map
New submission from Terry J. Reedy [EMAIL PROTECTED]:
StdLibMan Built-in Functions
I believe that at one time this section only contained functions.
But this has not been true since at least 2.2.
Please add and Classes to the title and first sentence.
Possibly add ('callables') after and classes in the sentence to
introduce the generic term. This would at least slightly help the
sometimes confusion between 'function' as specific class and as generic
callable.
This change also applies to 2.6 (and earlier, but oh, well...).
3.0 entry for map() (now a class!) in this section. Please add
With multiple iterables, stops when the shortest iterable is exhausted
. (Copied from map.__doc__.)
What's New in 3.0: Stumbling Blocks: map entry: Add same sentence or
similar. I only checked help(map) and discovered the change because of
reading about itertools.imap and knowing that 3.0 map was derived?
copied? from that.
--
assignee: georg.brandl
components: Documentation
messages: 66228
nosy: georg.brandl, tjreedy
severity: normal
status: open
title: Doc: built-in callables and map
type: behavior
versions: Python 3.0
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2761
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2761] Doc: built-in callables and map
Benjamin Peterson [EMAIL PROTECTED] added the comment: Guido is doing 3.0 whatsnew. -- nosy: +benjamin.peterson, gvanrossum __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2761 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2761] Doc: built-in callables and map
Raymond Hettinger [EMAIL PROTECTED] added the comment: FWIW, I think the title is clearer as-is. While it is technically true that some entries are callables of various types, it is simpler to think of all of them as functions. The proposed change makes the docs harder to understand and less usuable though technical more correct. -- nosy: +rhettinger __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2761 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2761] Doc: built-in callables and map
Georg Brandl [EMAIL PROTECTED] added the comment: I agree with Raymond here. -- resolution: - rejected status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2761 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2761] Doc: built-in callables and map
Terry J. Reedy [EMAIL PROTECTED] added the comment: To the best of my memory, the fact that type(built_in_function_section_object) is sometimes 'type...' (soon to be 'class...') rather than 'built-in function...' has been a point of occasional confusion on c.l.p for years. Such confusion was part of a recent newbie post there. I actually suggested, only half jokingly, 'Built-in callables' (and got at least one positive response) but decided that that was both too general and maybe a bit obscure, even though the Language Reference has a section on Callables. Hence the more specific suggestion. Perhaps we need more newbie opinions as to which they find clearer. Even if the title is left alone, I urge the expansion of the first sentence, though 'and callable classes' might be better. The double use of 'function' is definitely an occasional point of confusion in Python I think the crux of our disagreement is alternate parsings of 'built-in functions': 1) 'built-in' instances of generic concept 'function', 2) instances of specific class 'built-in function'. Under 1) the current title is fine. Under 2), it is not, and 'built-in functions and classes', interpreted as parsing 2 of 'built-in functions and [built-in] classes' is better. The map doc issues are, of course, separate from the title and lead sentence issue. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2761 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
