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

2011-03-22 Thread Roundup Robot
Roundup Robot devnull@devnull 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

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

2011-03-22 Thread Raymond Hettinger
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- resolution: - fixed status: open - closed versions: +Python 2.7, Python 3.1, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10610

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

2010-12-03 Thread Marc-Andre Lemburg
Marc-Andre Lemburg m...@egenix.com added the comment: Alexander Belopolsky wrote: Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Should we also review the documentation for fractions and decimals? For example, fractions are documented as accepting strings of

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

2010-12-03 Thread Marc-Andre Lemburg
Marc-Andre Lemburg m...@egenix.com added the comment: Raymond Hettinger wrote: Raymond Hettinger rhettin...@users.sourceforge.net 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.

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

2010-12-02 Thread Marc-Andre Lemburg
New submission from Marc-Andre Lemburg m...@egenix.com: 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

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

2010-12-02 Thread Mark Dickinson
Changes by Mark Dickinson dicki...@gmail.com: -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10610 ___ ___

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

2010-12-02 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com 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,

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

2010-12-02 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10610 ___ ___ Python-bugs-list

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

2010-12-02 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net 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

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

2010-12-02 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net 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

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

2010-12-02 Thread Raymond Hettinger
Raymond Hettinger rhettin...@users.sourceforge.net 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:

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

2010-12-02 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Fri, Dec 3, 2010 at 12:10 AM, Raymond Hettinger rep...@bugs.python.org 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

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

2010-12-02 Thread Raymond Hettinger
Raymond Hettinger rhettin...@users.sourceforge.net 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 rep...@bugs.python.org

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

2010-12-02 Thread Raymond Hettinger
Changes by Raymond Hettinger rhettin...@users.sourceforge.net: -- Removed message: http://bugs.python.org/msg123190 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10610 ___

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

2010-12-02 Thread Raymond Hettinger
Raymond Hettinger rhettin...@users.sourceforge.net 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