Hello,
Thanks for reporting the bug. I hope one of the few core devs with
Windows knowledge will be able to help me.
> I agree that reading bug comments by core devs is really frustrating,
> especially since distutils is frozen (which means for them that bugs
> don't get fixed)
No, it means th
I didn't bother to report that particular issue since
http://bugs.python.org/issue4709 (which has been reported nearly 4 years
ago) isn't being fixed and I can't provide a testcase that fails...
Other bugs that I hit when using mingw-w64:
http://bugs.python.org/issue11566
http://bugs.python.org/
Chris Jerdonek writes:
>> My guess would be that it's needed for some older gcc version. It looks
>> like none of the python developers care enough to fix issues with
>> mingw-w64.
>
> Has someone already tried filing an issue about this on the tracker
> (bugs.python.org)? Otherwise, I wouldn't
On Nov 12, 2012, at 5:36 AM, Ralf Schmitt wrote:
> Václav Šmilauer writes:
>
>> Hi everybody,
>>
>> I recently (inconclusively) discussed on the mingw-w64 mailing list
>> why are compiled modules linked to msvcrt90 (depending on python
>> build) rather than to msvcrt. A compiled module was crash
Václav Šmilauer writes:
> Hi everybody,
>
> I recently (inconclusively) discussed on the mingw-w64 mailing list
> why are compiled modules linked to msvcrt90 (depending on python
> build) rather than to msvcrt. A compiled module was crashing (the DLL
> would not load with "invalid access to memor
Hi everybody,
I recently (inconclusively) discussed on the mingw-w64 mailing list why
are compiled modules linked to msvcrt90 (depending on python build)
rather than to msvcrt. A compiled module was crashing (the DLL would not
load with "invalid access to memory and such") with msvcr90, while
