This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zwelch
Recipients steve.dower, tim.golden, zach.ware, zwelch
Date 2015-01-20.23:38:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421797130.26.0.795700230332.issue23199@psf.upfronthosting.co.za>
In-reply-to
Content
That's certainly an interesting data point.  We are just beginning to use MinGW-w64 internally, so I do not have enough experience to confirm or deny that advice.  For various reasons, we must use cross-compiling on a Linux host, so the advice to use a native compiler is moot for our situation.

Certainly, documenting the absense of the 64-bit library would be good.  Providing a documented script to generate one is better.  Providing the library would be ideal, if there will not be forward compatibility or runtime issues.

It would be nice to see concrete details about the current state of affairs.  The cython project's warning would carry more weight with me if it contained links to specific details: mailing list discussion that led to the "deliberate" decision to omit the 64-bit library, bug reports filed against the mingw-w64 project about the "runtime issues", etc..  That said, such details probably do exist, but my cursory searching has failed to turn them up.
History
Date User Action Args
2015-01-20 23:38:50zwelchsetrecipients: + zwelch, tim.golden, zach.ware, steve.dower
2015-01-20 23:38:50zwelchsetmessageid: <1421797130.26.0.795700230332.issue23199@psf.upfronthosting.co.za>
2015-01-20 23:38:50zwelchlinkissue23199 messages
2015-01-20 23:38:50zwelchcreate