Mailman 3 December 2012 - docs

[issue10589] I/O ABC docs should specify which methods have implementations
by Andrew Svetlov Dec. 6, 2012

Dec. 6, 2012

Andrew Svetlov added the comment: Fixed in a58204570a7c, 3cb85250a0a3, 93742b046519. ---------- assignee: stutzbach -> asvetlov resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10589> _______________________________________

1 0

PEP 415
by Guth, Dwight Dec. 5, 2012

Dec. 5, 2012

This page: http://docs.python.org/3.3/whatsnew/3.3.html Needs to list PEP 415 in the see also for PEP 409, since PEP 409's implementation is out of date and no longer applies.

1 0

[issue8402] Add a function to escape metacharacters in glob/fnmatch
by Serhiy Storchaka Dec. 5, 2012

Dec. 5, 2012

Serhiy Storchaka added the comment: It is good, if stdlib has function for escaping any special characters, even if this function is simple. There are already escape functions for re and sgml/xml/html. Private function glob.glob1 used in Lib/msilib and Tools/msi to prevent unexpected globbing in parent directory name. ``glob.glob1(dirname, pattern)`` should be replaced by ``glob.glob(os.path.join(fnmatch.escape(dirname), pattern)`` in external code. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8402> _______________________________________

1 0

[issue16609] float loses precision when passed to str()
by Cal Leeming Dec. 4, 2012

Dec. 4, 2012

Changes by Cal Leeming <cal.leeming(a)simplicitymedialtd.co.uk>: ---------- status: open -> pending _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16609> _______________________________________

1 0

[issue16609] float loses precision when passed to str()
by Cal Leeming Dec. 4, 2012

Dec. 4, 2012

Cal Leeming added the comment: Actually, you do have a good point, this should have been using random.getrandbits really. ---------- status: pending -> open _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16609> _______________________________________

1 0

[issue16609] float loses precision when passed to str()
by Antoine Pitrou Dec. 4, 2012

Dec. 4, 2012

Antoine Pitrou added the comment: I agree with Mark here. This isn't specific to random.random() and it's already covered elsewhere in the documentation. Furthermore, I don't know why you're using str() on random.random(). There are better ways to get random strings, such as random.getrandbits() or os.urandom(). Recommend closing. ---------- nosy: +pitrou resolution: -> invalid status: open -> pending _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16609> _______________________________________

1 0

[issue16609] float loses precision when passed to str()
by R. David Murray Dec. 4, 2012

Dec. 4, 2012

R. David Murray added the comment: That's why I suggested a glossary entry. The relevant function description *does* contain the phrase "floating point", so a glossary link there would be reasonably natural. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16609> _______________________________________

1 0

[issue16609] float loses precision when passed to str()
by Mark Dickinson Dec. 4, 2012

Dec. 4, 2012

Changes by Mark Dickinson <dickinsm(a)gmail.com>: ---------- title: random.random() / float() loses precision when passed to str() -> float loses precision when passed to str() _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16609> _______________________________________

1 0

[issue16609] random.random() / float() loses precision when passed to str()
by Mark Dickinson Dec. 4, 2012

Dec. 4, 2012

Mark Dickinson added the comment: It is notable that this behaviour isn't described anywhere that I can find in the library manual or the reference manual. As David says, it applies only to 2.7; in 3.2 and later, `str` and `repr` are identical. > a glossary entry be added for 'floating point' which mentions it as a > 2.7 limitation That could work. I *really* don't think it should be linked to from the random docs, though; this has absolutely nothing to do with the random module, except that the random module happens to contain functions that can produce floats. Many other modules do that, too. Another option would be to add the information somewhere in http://docs.python.org/2/library/stdtypes.html#numeric-types-int-float-long… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16609> _______________________________________

1 0

[issue16609] random.random() / float() loses precision when passed to str()
by Cal Leeming Dec. 4, 2012

Dec. 4, 2012

Cal Leeming added the comment: Many thanks for your lengthy response David. Sorry, my initial bug report stated it was Python 2.7. The tests I performed were actually on Python 2.6.6. I will take a look at how to contribute documentation updates, and once I've familiarized myself with it I'll submit a patch for review. Thanks again ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16609> _______________________________________

1 0