I haven't heard much from people using IronPython. I had assumed that the project was somewhat dead. I'd be happy to work around bugs. The biggest issue for us is testing it. You have to have Windows (I tried using Mono a while back, but I didn't have much luck). There is this open issue https://github.com/sympy/sympy/issues/3159.
Maybe there are other ways to either call Python from C# or call C# from Python. I've always thought that using a glue library was a better approach than trying to reimplement all of Python in .NET (or whatever language). You could probably make your own poor-man's glue by just calling some Python script in a subprocess. Aaron Meurer On Sat, Apr 5, 2014 at 2:00 PM, Groover <[email protected]> wrote: > Thanks for explaining the integrand mistake. It is correct in the SymPy > code and incorrect in the calculator. > > I guess I am stuck between a rock and a hard place. The primary purpose of > my (free) application is to interface with a CAD package. The 3rd party > interface uses .NET, so I naturally choose C# and IronPython for the > development. Now I would like to add more functionality to the python side > and I thought that SymPy was a nice fit. But it seems I am not going to be > able to get it working with IronPython. > > From the other way around - developing a CAD interface library for > Anaconda for example - also seems to be fraught with problems if the > library uses .NET. There are vague mentions of python to .NET bridges but > that doesn't seem a popular approach. > > Sigh. :( > > Andy > > > On Saturday, April 5, 2014 7:27:25 PM UTC+1, Matthew wrote: >> >> They are the same. I was just suggesting x**y over pow(x, y). Mostly >> because that's my aesthetic preference. Feel free to ignore. >> >> By googling unicode_escape_decode() takes no arguments I run into a >> stackoverflow question that references using Python from F# so I'm going to >> guess that this is more of an IronPython than a SymPy problem. >> >> My guess is that your other issue boils down to this as well. It looks >> like IronPython doesn't naturally expand iterators (it mentions >> dictionary-itemgetter) when used with the * operator. >> >> Question to the community, should we endeavor to support IronPython in >> the same way that we support CPython 2, 3, and PyPy? >> Question to Andy, do you have a sense of how big the IronPython community >> that might use SymPy is? This is probably important information to answer >> the previous question. >> >> Regarding your integrand. d is 4x. In the SymPy code you square this >> giving 16x^2 within the integrand. In the link you posted you're only >> squaring x, not 4x, and so you get 4*x^2. >> >> -Matt >> >> -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/b337d123-9ec0-4772-bc2a-94f616b9de53%40googlegroups.com<https://groups.google.com/d/msgid/sympy/b337d123-9ec0-4772-bc2a-94f616b9de53%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2BHMhO2DPD%3DnBsRyHiBLcf%3DfXLt1ZKZXvKCwdwd-X_hKA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
