On 08/08/2010 11:15 AM, Stefan Behnel wrote: > Dag Sverre Seljebotn, 06.08.2010 11:31: > >> Mono support could be important *long-term*, because it allows all the >> non-Windows users to not break things on the .NET side when developing >> and merging patches. One can include Mono builds in build farms, whether >> it is Cython, NumPy, SciPy etc. >> >> For that purpose Wine could work as well though if .NET is well >> supported in Wine. Well, given some common scientific Python build farm >> infrastructure (where Sage and Enthought pools together?), even >> VirtualBox would be workable. But at the end of the day, Mono will >> always be more convenient to set up for Linux devs. >> > Actually, .NET not being portable pretty much rules out any use case I > might have for it. Mono is the only reason for me to consider IronPython a > viable alternative to CPython. >
I think the main point of the .NET Cython port is to allow libraries to also target .NET. I.e. I don't think many of the *current* CPython users will really use it themselves (Mono or not), it is all about reaching out to *new* users who are currently using .NET . The usefulness of this depends, of course, very much on the library in question. For SciPy and NumPy there is definitely a demand (IronClad was developed to run NumPy IIRC). Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
