RetroSearch Browse

Mon Jul 11 02:28:24 EDT 2016 · https://mail.python.org/pipermail/python-dev/2016-July/145568.html

On Mon, Jul 11, 2016 at 4:25 PM, Ethan Furman <ethan at stoneleaf.us> wrote:
> On 07/10/2016 08:32 PM, Chris Angelico wrote:
>>
>> On Mon, Jul 11, 2016 at 1:26 PM, Steven D'Aprano <steve at pearwood.info>
>> wrote:
>>>
>>> (1) How much extra effort are we going to *mandate* that core devs put
>>> in to hide the differences between C and Python code, for the benefit of
>>> a small minority that will notice them?
>>>
>>
>> The subject line is raising one specific difference: the use of a
>> function in one version and a class in the other. I think it's not
>> unreasonable to stipulate one specific incompatibility that mustn't be
>> permitted.
>
>
> Is that what the subject line meant?  I missed that, thanks for pointing
> that out!
>
> I think I can agree with having both versions being functions or both
> versions being classes.
>

What I mean is, the subject line is ONLY raising that one difference.
If the C version of a class has no __dict__ but the Python version
does, that's not as big a difference.

ChrisA

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-July/145568.html below:

[Python-Dev] Proposal: explicitly disallow function/class mismatches in accelerator modules