[Cython] heads-up on master branch status

[Robert Bradshaw]

Ironically, I noticed these BoolBinop failures and started working on a fix
myself (including side diversions like making void* the spanning type of
all pointers) before noticing that you were on it, so I have a bit of an
idea what a long, twisty path this starts down and can only say thanks for
taking this on.

- Robert



On Mon, Jul 14, 2014 at 12:49 PM, Stefan Behnel <stefan_ml at behnel.de> wrote:

> Hi,
>
> by applying some initially small but perpetually growing fixes, I pushed
> myself into a corner where the only escape was to rewrite BoolBinopNode
> (short-circuiting and/or expressions). This was long overdue anyway and
> simply wasn't done before because it's not trivial and quite risky. I think
> I got it working better than before, but there are still corner cases that
> require some further fighting. One of them currently crashes the pyregr
> tests in Py2.7, it's this code:
>
>     [tuple((e is None and 'X' or e) for e in t) for t in target]
>
> Thank you, python-devs, for collecting these little gems in the test suite.
> From the C code this generates, the problem seems to be related to type
> coercion in closures. I'm currently preparing my participation at
> EuroPython next week, so I can't tell for sure when I'll be able to dig
> into this. This means that current master may stay less stable than it
> should be for a couple of more days.
>
> Stefan
> _______________________________________________
> cython-devel mailing list
> cython-devel at python.org
> https://mail.python.org/mailman/listinfo/cython-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cython-devel/attachments/20140715/0af2a422/attachment.html>