Robert Bradshaw wrote: > On Thu, Aug 5, 2010 at 9:55 PM, Carl Witty <[email protected]> wrote: > >> On Thu, Aug 5, 2010 at 8:26 PM, Robert Bradshaw >> <[email protected]> wrote: >> >>> On Thu, Aug 5, 2010 at 9:58 AM, Carl Witty <[email protected]> wrote: >>> >>>> Once the C++/CLI backend works, a C# backend is a possible next step. >>>> All of the code generation for C# to interface with IronPython would >>>> be exactly the same as C++/CLI (modulo minor syntactic issues that can >>>> easily be localized). Even if the ultimate goal is a C# backend, I >>>> think that very little of the work on a C++/CLI backend would be >>>> wasted. >>>> >>> The ultimate goal is really just Cython working (well) for IronPython, >>> right? How essential is C# generation (vs. C++/CLI) to that goal? >>> >> For IronPython running under Microsoft's .NET implementation for >> Windows, as far as I know there are no problems with C++/CLI. For >> IronPython running under Mono on non-Windows platforms, C++/CLI >> doesn't help at all; there are no implementations of C++/CLI on >> non-Windows platforms and no effort toward making an implementation. >> So the purpose of a C# backend would be to support Mono. >> > > Ah. As much as I support the Mono project, I would imagine that most > Mono users who wanted to use Python would just use CPython directly > (though I wouldn't rule out any usecase of IronPython on Mono). Of > course this is just pure speculation, I don't follow the Mono project > very closely. If it comes out naturally once the C++/CLI is going well > that would be a huge plus. > 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. Ignoring it short-term shouldn't hurt though. Also, though I don't really know, it might be that Cython+C# would beat Cython+CPython performance wise for non-typed Python stuff. And no GIL! CPython could get its act together with a LLVM backend etc., but it would be nice strategically to have Mono available as a competing platform, in case CPython doesn't manage to improve matters. Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
