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 skrah
Recipients docs@python, skrah
Date 2011-08-25.20:31:24
SpamBayes Score 3.988037e-06
Marked as misclassified No
Message-id <1314304285.47.0.471516118599.issue12842@psf.upfronthosting.co.za>
In-reply-to
Content
I've noticed that assumptions about the operand types in tp_richcompare()
are not always consistent. As far as I can see, the first parameter
in tp_richcompare() is guaranteed to be of the correct type.

But in some places the first parameter's type is still checked:

Objects/cellobject.c:

    if (!PyCell_Check(a) || !PyCell_Check(b)) {


The attached patch makes it clear that the first parameter has
the correct type.
History
Date User Action Args
2011-08-25 20:31:25skrahsetrecipients: + skrah, docs@python
2011-08-25 20:31:25skrahsetmessageid: <1314304285.47.0.471516118599.issue12842@psf.upfronthosting.co.za>
2011-08-25 20:31:24skrahlinkissue12842 messages
2011-08-25 20:31:24skrahcreate