This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Doug Hoskisson, docs@python, r.david.murray, rhettinger, vstinner
Date 2016-07-27.18:41:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469644864.76.0.0917068252597.issue27624@psf.upfronthosting.co.za>
In-reply-to
Content
The current wording is, IMO, better than the suggested wording, especially if you don't want to be "teaching stuff".  The current wording is a specification of the method's behavior.  I really don't know what you could replace "approximate" with that would improve it without having to get into a description of the behavior of a threaded program.

It seems like you are wanting us to document that the function will return an accurate size if the program is single threaded, but I don't think we want to do that, because that is not part of the specification of the method.
History
Date User Action Args
2016-07-27 18:41:04r.david.murraysetrecipients: + r.david.murray, rhettinger, vstinner, docs@python, Doug Hoskisson
2016-07-27 18:41:04r.david.murraysetmessageid: <1469644864.76.0.0917068252597.issue27624@psf.upfronthosting.co.za>
2016-07-27 18:41:04r.david.murraylinkissue27624 messages
2016-07-27 18:41:04r.david.murraycreate