[Python-Dev] Proposal: explicitly disallow function/class mismatches in accelerator modules
Chris Angelico
rosuav at gmail.com
Mon Jul 11 02:28:24 EDT 2016
More information about the Python-Dev mailing list
Mon Jul 11 02:28:24 EDT 2016
- Previous message (by thread): [Python-Dev] Proposal: explicitly disallow function/class mismatches in accelerator modules
- Next message (by thread): [Python-Dev] Proposal: explicitly disallow function/class mismatches in accelerator modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): [Python-Dev] Proposal: explicitly disallow function/class mismatches in accelerator modules
- Next message (by thread): [Python-Dev] Proposal: explicitly disallow function/class mismatches in accelerator modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list