[Cython] 0.20.1 bug fix release

Stefan Behnel stefan_ml at behnel.de
Tue Feb 4 11:07:15 CET 2014


Robert Bradshaw, 04.02.2014 08:33:
> On Fri, Jan 31, 2014 at 3:49 AM, Stefan Behnel wrote:
>> Stefan Behnel, 30.01.2014 17:40:
>>> Robert Bradshaw, 29.01.2014 19:10:
>>>> Ouch. Between this and the other Sage issue, I feel a small point
>>>> release coming up. Any other bug fixes we should get in?
>>>
>>> I have a couple of pending requests for others to test lxml on Windows and
>>> maybe even PyPy, so let's wait another couple of days for them to report
>>> back. I don't see any notable changes coming.
>>
>> All confirmed that it works now, so I'm fine with getting the bug fix
>> release rolling.
> 
> I've been looking through the changes, and most seem fairly safe

I guess you saw the CyFunction struct layout change? Given that the type
sharing is done at a per-version level, even that should be safe.


> Is there anything in master that shouldn't go in?

Well, given that there currently isn't a CPython 3.4 pre-release that
actually triggers the tests I added, it's a bit of a bet to keep them in. I
tried them on my local checkout, but there is still some churn and
discussion going on in CPython, which means that some things can still change.

OTOH, the worst thing that can happen is that we end up with a point
release where some tests will fail in a future Py3.4 release, and that we'd
need yet another point release for the final Py3.4 support (which we may
need anyway, because it's a moving target as of now). So, I don't think
releasing master as it is really hurts anyone.

Stefan



More information about the cython-devel mailing list