2011/2/22 Stefan Behnel :
> Vitja Makarov, 20.02.2011 18:23:
>>
>> 2011/2/16 Vitja Makarov:
>>>
>>> Hmm... both python and codespeaks in the thread
>
> Yes, we should keep it to cython-devel only. Sorry for mixing it up.
>
>
>>> Here is my commit it's mostly broken now but anyway
>>>
>>> https://gi
On 22 February 2011 19:09, Lisandro Dalcin wrote:
> On 22 February 2011 18:21, Stefan Behnel wrote:
>> Lisandro Dalcin, 22.02.2011 21:41:
>>>
>>> I'm inclined to fix the behavior for ALL Python
>>> versions to suppress only AttributeError.
>>
>> How? Would you implement a hasattr() helper that us
On 22 February 2011 18:21, Stefan Behnel wrote:
> Lisandro Dalcin, 22.02.2011 21:41:
>>
>> I'm inclined to fix the behavior for ALL Python
>> versions to suppress only AttributeError.
>
> How? Would you implement a hasattr() helper that uses PyObject_GetAttr() and
> Does The Right Thing?
>
Yes, m
Lisandro Dalcin, 22.02.2011 21:41:
Take a look here: http://bugs.python.org/issue9666
'hasattr' default behaviour should be changed to suppress only
AttributeError exceptions. Other should pass through.
+1, I think I even faintly recall that discussion. What a lengthy thread...
http://mail.p
Take a look here: http://bugs.python.org/issue9666
'hasattr' default behaviour should be changed to suppress only
AttributeError exceptions. Other should pass through.
Should we do something about this in Cython? We currently use
PyObject_HasAttr(), but even in Python 3.2 this is not the same as
Vitja Makarov, 20.02.2011 18:23:
2011/2/16 Vitja Makarov:
Hmm... both python and codespeaks in the thread
Yes, we should keep it to cython-devel only. Sorry for mixing it up.
Here is my commit it's mostly broken now but anyway
https://github.com/vitek/cython/commit/5579b23c3c1c06981331b6427
On Tue, Feb 22, 2011 at 08:18:21PM +0100, Stefan Behnel wrote:
> W. Trevor King, 22.02.2011 18:55:
> > I've been working on a more explicit parser that removes the ambiguity
> > behind the various visibilities. This will help me ensure proper
> > impolementation of my cdef-ed enums/structs/..., an
W. Trevor King, 22.02.2011 18:55:
I've been working on a more explicit parser that removes the ambiguity
behind the various visibilities. This will help me ensure proper
impolementation of my cdef-ed enums/structs/..., and make it easier to
update visibility syntax in the future. Take a look an
On Sat, Feb 19, 2011 at 06:31:26PM -0500, W. Trevor King wrote:
> On Sat, Feb 19, 2011 at 02:04:16PM -0800, Robert Bradshaw wrote:
> > On Sat, Feb 19, 2011 at 1:45 PM, W. Trevor King wrote:
> > > Ah. Sorry for all the c(p)def/qualifier confusion, but I'm trying to
> > > consolidate the way these
