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 facundobatista, mark.dickinson, rhettinger, serhiy.storchaka, skrah
Date 2016-07-16.22:09:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468706968.98.0.589076272708.issue26974@psf.upfronthosting.co.za>
In-reply-to
Content
The approaches look good, but for clarity I want to replace all method calls that should never be overridden by the plain C functions of their corresponding static types.

I have no opinion about the Python version. The diff also "fixes" #26975 for the C version, so perhaps the Python version should be in sync. It is an academic question, since no one will write a class that triggers it.

Preemptively, I'm aware that long_bit_length() is defined with a single argument, then cast to a CFunction, then called with two arguments.

ceval.c does the same. -- We had a discussion about that with MvL a while ago, he preferred to define all CFunctions with two arguments. I'd also prefer that, but that is another issue.
History
Date User Action Args
2016-07-16 22:09:29skrahsetrecipients: + skrah, rhettinger, facundobatista, mark.dickinson, serhiy.storchaka
2016-07-16 22:09:28skrahsetmessageid: <1468706968.98.0.589076272708.issue26974@psf.upfronthosting.co.za>
2016-07-16 22:09:28skrahlinkissue26974 messages
2016-07-16 22:09:28skrahcreate