➜

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 mark.dickinson
Recipients Mark.Shannon, georg.brandl, mark.dickinson, r.david.murray
Date 2010-09-23.19:50:24
SpamBayes Score 2.905161e-07
Marked as misclassified No
Message-id <1285271426.43.0.562174618581.issue9930@psf.upfronthosting.co.za>
In-reply-to
Content 
It looks like Mark is right:  the wrap_binaryfunc_r subtype check should just be removed.  The corresponding check in 2.x only occurs for types which don't have the Py_TPFLAGS_CHECKTYPES flag set.  As of 2.7, *all* of the numeric types have this flag set (in 2.6, the complex type doesn't).

I'm not seeing any (relevant) test failures here after removing the check.
Actually, I'm not seeing any test failures at all.  Hooray!
History
Date User Action Args
2010-09-23 19:50:26mark.dickinsonsetrecipients: + mark.dickinson, georg.brandl, r.david.murray, Mark.Shannon
2010-09-23 19:50:26mark.dickinsonsetmessageid: <1285271426.43.0.562174618581.issue9930@psf.upfronthosting.co.za>
2010-09-23 19:50:25mark.dickinsonlinkissue9930 messages
2010-09-23 19:50:24mark.dickinsoncreate