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 r.david.murray, terry.reedy
Date 2009-03-17.13:47:27
SpamBayes Score 2.4430435e-09
Marked as misclassified No
Message-id <1237297649.61.0.225264594791.issue5353@psf.upfronthosting.co.za>
In-reply-to
Content
This issue was discussed two years ago in this thread:

http://mail.python.org/pipermail/python-list/2006-December/588224.html

Most of the messages under that subject are noise about politeness or
lack thereof (including a post by the submitter of this issue trying to
get people to be reasonable!), but an actual patch was posted as well:

http://mail.python.org/pipermail/python-list/2006-December/588377.html

The patch addresses only one object type, but does demonstrate a pattern
that might be usable in general.  A concern was raised about the
generality of the function proposed, as well as the performance
implications of calling it.

I have not tried to apply the patch to the current trunk, but from a
quick look it doesn't seem like the source has changed much.  Since the
problem turns out to be a lot less trivial than it seems like it should
be, the patch is a good reference in any case.
History
Date User Action Args
2009-03-17 13:47:29r.david.murraysetrecipients: + r.david.murray, terry.reedy
2009-03-17 13:47:29r.david.murraysetmessageid: <1237297649.61.0.225264594791.issue5353@psf.upfronthosting.co.za>
2009-03-17 13:47:28r.david.murraylinkissue5353 messages
2009-03-17 13:47:27r.david.murraycreate