[Cython] longintrepr.h issues with MinGW

Stefan Behnel stefan_ml at behnel.de
Wed Oct 24 00:53:06 EDT 2018

Robert Bradshaw schrieb am 24.10.2018 um 01:44:
> On Tue, Oct 23, 2018 at 10:22 PM Stefan Behnel wrote:
>> My guess is that MinGW is just fairly rarely used to build CPython
>> extensions overall.
>>> but perhaps we should even consider releasing bugfixes for previous
>>> Cython versions.
>> You mean a 0.28.6, or even older than that?
> I wish there were a good way to see what users are actually using in the wild...

At least from what I hear from time to time, many people tend to stick to
whatever was there when they started using Cython, and then manually
upgrade in irregular intervals whenever they feel like they need something
from a newer version.

Especially in-house, something like, say, 0.23 might still be in use. But
then, we don't really need to care about in-house use of this, because
people control their environment and their C compiler there. If they didn't
experience this bug yet, then it's probably not a problem for them at all.

Regarding more widely used libraries that are used across different
environments, I'd say that they'd probably have added support for CPython
3.7 by now. Anything before Cython 0.28 didn't even compile there, and 0.29
is recommended for it, so I think we can somewhat safely assume that this
bug is most pressing for those two versions.

Thanks to Mark Shannon for raising the baseline here. :)

>> As I said, MinGW does not seem to be used very widely…
> Yes, but it is used, and this is (IMHO) a really severe bug.

Agreed. Let's release a 0.28.6 with this fix and move on to 0.29.1.


More information about the cython-devel mailing list