[issue10610] Correct the float(), int() and complex() documentation

Changes by Raymond Hettinger : -- resolution: -> fixed status: open -> closed versions: +Python 2.7, Python 3.1, Python 3.3 ___ Python tracker ___ __

[issue10610] Correct the float(), int() and complex() documentation

Roundup Robot added the comment: New changeset 6853b480e388 by Raymond Hettinger in branch '3.1': Issue #10610: Document that int(), float(), and complex() accept numeric literals with the Nd property. http://hg.python.org/cpython/rev/6853b480e388 New changeset a1e685ceb3bd by Raymond Hettinge

[issue10610] Correct the float(), int() and complex() documentation

Marc-Andre Lemburg added the comment: Raymond Hettinger wrote: > > Raymond Hettinger added the comment: > > Try not to sprawl this all over the docs. Find the most common root and > document it there. No need to garbage-up Fractions, Decimal etc. with > something that is of zero interest

[issue10610] Correct the float(), int() and complex() documentation

Marc-Andre Lemburg added the comment: Alexander Belopolsky wrote: > > Alexander Belopolsky added the comment: > > Should we also review the documentation for fractions and decimals? For > example, fractions are documented as accepting "strings of decimal digits", > but given that we have p

[issue10610] Correct the float(), int() and complex() documentation

Raymond Hettinger added the comment: Let me know when you have a proposed doc patch. Ideally, the details should just be in one place and we can refer to it elsewhere. We don't want to add extra info to every function or method in Python that uses int(s) and gets extra unicode digits as an

[issue10610] Correct the float(), int() and complex() documentation

Changes by Raymond Hettinger : -- Removed message: http://bugs.python.org/msg123190 ___ Python tracker ___ ___ Python-bugs-list mailin

[issue10610] Correct the float(), int() and complex() documentation

Raymond Hettinger added the comment: Try not to twist yourself in a knot over this. I'll be happy to review in proposed doc patch. -- assignee: d...@python -> rhettinger ___ Python tracker ___

[issue10610] Correct the float(), int() and complex() documentation

Alexander Belopolsky added the comment: On Fri, Dec 3, 2010 at 12:10 AM, Raymond Hettinger wrote: .. > Try not to sprawl this all over the docs.  Find the most common root and > document it there. > No need to garbage-up Fractions, Decimal etc. with something that is of zero >interest to > 99

[issue10610] Correct the float(), int() and complex() documentation

Raymond Hettinger added the comment: Try not to sprawl this all over the docs. Find the most common root and document it there. No need to garbage-up Fractions, Decimal etc. with something that is of zero interest to 99.9% of users. -- nosy: +rhettinger

[issue10610] Correct the float(), int() and complex() documentation

Alexander Belopolsky added the comment: Should we also review the documentation for fractions and decimals? For example, fractions are documented as accepting "strings of decimal digits", but given that we have presumably non-identical str.isdigit() and str.isdecimal() methods, the above def

[issue10610] Correct the float(), int() and complex() documentation

Alexander Belopolsky added the comment: Marc, I don't want to further sprawl the python-dev thread, but it would be great if you could help with issue10587 as well. That is a documentation-only issue, but there is some disagreement about how specific the docs should be. Some of the relevan

[issue10610] Correct the float(), int() and complex() documentation

Changes by Terry J. Reedy : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10610] Correct the float(), int() and complex() documentation

Mark Dickinson added the comment: The reference to the language spec was really just a way to avoid spelling out all the details (again) about the precise form of a floating-point string; apart from the accepted set of digits, the forms are exactly the same (optional sign, numeric part, opti

[issue10610] Correct the float(), int() and complex() documentation

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue10610] Correct the float(), int() and complex() documentation

New submission from Marc-Andre Lemburg : The Python3 documentation for these numeric constructors is wrong. Python has supported Unicode numerals specified as code points from the Unicode category "Nd" (decimal digit) since Python 1.6.0 when Unicode was first introduced in Python. http://