I remember this being discussed here: http://codespeak.net/pipermail/cython-dev/2008-May/000844.html
Was this resolved back then? -------- Original Message -------- Subject: [Numpy-discussion] VS 2003 problems with cython-generated code Date: Fri, 15 Aug 2008 11:49:28 -0500 From: David Cournapeau <[EMAIL PROTECTED]> Reply-To: Discussion of Numerical Python <[EMAIL PROTECTED]> To: Discussion of Numerical Python <[EMAIL PROTECTED]> Hi, I noticed this morning that numpy 1.2 is not buildable with VS 2003 (the one you have to use for official python releases for at least python 2.5, and maybe 2.4). When we generate C code, both with internal code (numpy/core/code_generator) and with external tools (cython/pyrex for mtrand), the string literals generated for docstrings are too long for visual studio. We have to break them (e.g. "foo bar" becomes "foo""bar"), but doing so with cython-generated code is only doable by changing cython itself. So I did patch cython to break those, and regenerate the mtrand.c. This is done in the vs_longstring branch. Is it ok to put this for 1.2 ? Without it, I don't see a way to have numpy 1.2 buildable with VS. cheers, David P.S: I attached the necessary patches to cython bug tracker too, so that hopefully, the problem can be solved for a future version of cython. _______________________________________________ Numpy-discussion mailing list [EMAIL PROTECTED] http://projects.scipy.org/mailman/listinfo/numpy-discussion -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
