[issue14783] Update int() docstring from manual

Ezio Melotti added the comment: Here's a patch for the signature. -- assignee: -> ezio.melotti keywords: +patch stage: needs patch -> commit review Added file: http://bugs.python.org/file27075/issue14783.diff ___ Python tracker

[issue14783] Update int() docstring from manual

Éric Araujo added the comment: +1! This notation helps clearing up how int, str and other constructors work. -- nosy: +eric.araujo ___ Python tracker ___ ___

[issue14783] Update int() docstring from manual

Ezio Melotti added the comment: .. function:: int(n=0) int(s, base=10) should do the trick. +1 on using this instead of int([number | string[, base]]) -- ___ Python tracker __

[issue14783] Update int() docstring from manual

Raymond Hettinger added the comment: The 3.3 version has the virtue of being accurate and the vice of being confusing. In a way, it has made the docs worse for the average user of common cases. Is there a way to stack the alternative signatures rather than mush the various used into a single

[issue14783] Update int() docstring from manual

Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue14783] Update int() docstring from manual

Changes by Ezio Melotti : -- assignee: docs@python -> nosy: +ezio.melotti stage: -> needs patch type: -> enhancement ___ Python tracker ___ ___

[issue14783] Update int() docstring from manual

Changes by Tshepang Lekhonkhobe : -- assignee: -> docs@python components: +Documentation nosy: +docs@python, tshepang ___ Python tracker ___

[issue14783] Update int() docstring from manual

New submission from Terry J. Reedy : int.__doc__ starts "int(x[, base]) -> integer". That is not exactly correct as x is not required and base is only allowed if x is a string. The 3.3 manual fixes both problems with "int([number | string[, base]])" I actually think the rest of the docstring m