Sorry, I somehow missed the rest of your post...
Lisandro Dalcin wrote:
>> Anyway, I think we can conclude already that this is controversial
>> enough to demand a CEP? It's been up several times in the past with the
>> same arguments reiterated IIRC.
>>
>>
>
> Given the scarce time Stefan and me have for this, asking for a CEP is
> an obvious way to maintain the status-quo ;-) ...
>
Heh, I guess...
I actually forgot somewhere in the heat that your request was for a
compiler directive turned off by default. Sorry about that. Yes, I can
see that for e.g. lxml and mpi4py such a directive would be more useful
than it would be for me.
I'll yield my opposition towards a directive turned off by default,
provided the name is clear enough ("check_arguments_for_none",
"no_none_arguments"...?).
Dag Sverre
> Come on! I really do not understand... "not None" and "or None" are
> certainly not part of Python' semantics, nor are type declaration (a
> subject people use and abuse here for argumentation)... So, for the
> very moment I use a typed argument, I abandoned strict Python
> semantics, so I should be able to decide how to manage None in a
> case-by-case basis (using "Type arg not None", "Type arg or None", or
> "Type arg=None", etc.) and moreover I should be able to choose the
> default handling, i.e. use a COMPILER DIRECTIVE!!!
>
> I really cannot understand the opposition to the None handling being
> determined by a user-selected compiler directive... Of course, one
> this is available, we could have discussions, write CEP's, fight with
> swords, whatever.... about what should the default handling be if
> the directive is not used. I would probably not make any strong
> argument about this; I'm not a language lawyer; just a user how makes
> some contributions to core from time to time, had the experience of
> wrapping medium-sized C API's, and is upset of being forced to
> manually write "not None" in almost every method! Because if I forget
> to write "not None", my code is likely broken!!!
>
> PS: Even if 100% correct control flow is ever implemented and
> available, I would still like to use "Type arg not None", as that
> exposes errors early-on.
>
>
>
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
