[issue16503] Unclear documentation regarding apply(), 'extended call syntax'

2012-11-18 Thread Zachary Ware
Changes by Zachary Ware : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue16503] Unclear documentation regarding apply(), 'extended call syntax'

2012-11-18 Thread Zachary Ware
Zachary Ware added the comment: Looks good to me, thank you Ezio! -- resolution: fixed -> status: closed -> open type: enhancement -> ___ Python tracker ___ ___

[issue16503] Unclear documentation regarding apply(), 'extended call syntax'

2012-11-18 Thread Ezio Melotti
Ezio Melotti added the comment: It should be clearer now. -- assignee: docs@python -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> enhancement ___ Python tracker

[issue16503] Unclear documentation regarding apply(), 'extended call syntax'

2012-11-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7efa0d66b1a0 by Ezio Melotti in branch '2.7': #16503: clarify "apply" docs. http://hg.python.org/cpython/rev/7efa0d66b1a0 -- nosy: +python-dev ___ Python tracker _

[issue16503] Unclear documentation regarding apply(), 'extended call syntax'

2012-11-18 Thread Zachary Ware
New submission from Zachary Ware: (Reported by Kevin Leeds on d...@python.org) The documentation for the apply() built-in function in 2.7 says that it is deprecated and to use "extended call syntax" instead. There is no mention of "extended call syntax" anywhere else in the docs. The simples