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 exarkun
Recipients exarkun, pitrou
Date 2008-08-04.19:37:26
SpamBayes Score 0.00010416332
Marked as misclassified No
Message-id <1217878648.0.0.626907047575.issue3500@psf.upfronthosting.co.za>
In-reply-to
Content
The reason I noticed this is that since they compare and hash equal, if
you put two such methods into a set, you end up with a set with one
method.  Currently, this is preventing me from running two test methods
because the method itself is defined on a base class and two subclasses
which customize several other methods inherit it.  I can only run one
test at a time.

Having them compare unequal means you can't actually trust unbound
method comparison, nor using unbound methods as keys in a dictionary. 
This means some other mapping structure is required if you want to keep
around a bunch of methods and arguments to pass to them.  It also means
that any time you want to check two methods against each other with the
goal of eventually calling one or both of them, you need to use
something other than `==´.  It seems like calling methods is likely to
be a more common use-case than anything else.
History
Date User Action Args
2008-08-04 19:37:28exarkunsetrecipients: + exarkun, pitrou
2008-08-04 19:37:27exarkunsetmessageid: <1217878648.0.0.626907047575.issue3500@psf.upfronthosting.co.za>
2008-08-04 19:37:27exarkunlinkissue3500 messages
2008-08-04 19:37:26exarkuncreate