[Cython] Done with compiler options/pragmas

[Dag Sverre Seljebotn]

Stefan Behnel wrote:
> Hi,
> 
> Lisandro Dalcin wrote:
>> On Tue, Aug 5, 2008 at 9:49 AM, Dag Sverre Seljebotn
>>> Ways to set options:
>>> a)
>>> #cython: boundscheck=True, other=False
>>> #cython: third = no
>>>
>>> before any code in the file (but whitespace is allowed, I'm using
>>> Plex/the parser). The boolean value is case-insensitive and
>>> true/false/yes/no is allowed (is this too much? The thing is, for
>>> command-line arguments "True" is rather unfriendly and I'd like it to be
>>> consistent).
>> It is not to much at all. I would even ask for '1' and '0' also being
>> accepted for booleans.
> 
> I think they would be ok on the cmd line, yes.
> 
> 
>>> b) A command line argument "cython -O boundscheck=False,other=tRUe -O
>>> third=yes". This overrides the #cython comments, but NOT c) and d)
>>> listed below.
>> Well, '-O' smells to 'optimization' for me.
> 
> Yes, and Python uses it exactly for that.
> 
> "-X" has been "reserved for implementation-specific arguments" in Python 3 due
> to request by Jython (and IronPython?), maybe we should just use that.

Nice! +1

-- 
Dag Sverre