it appears to work for me:
$ bin/Debug/ipy -X:Frames -c 'import sympy; sympy.test()'
= test process starts ==
executable:
C:\cygwin64\home\rejap\github\IronLanguages\bin\Debug\ipy.exe
(2.9.9-alpha-0) [IronPython]
architecture: 32-bit
ca
Hi,
I didn't realize that SymPy has a test suite built in. Trying to run it
gives:
=
>>>sympy.test()
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files
(x86)\WizoScript\PythonLib\site-packages\sympy\utilities
On Thu, Apr 10, 2014 at 9:09 AM, Pawel Jasinski
wrote:
> I have opened a cp: https://ironpython.codeplex.com/workitem/35116
> I have a fix, but before push request I need to check if it doesn't
> break something else.
> It needs a to be reviewed and hopefully it is not to late for 2.7.5.
You'll
I have opened a cp: https://ironpython.codeplex.com/workitem/35116
I have a fix, but before push request I need to check if it doesn't
break something else.
It needs a to be reviewed and hopefully it is not to late for 2.7.5.
--pawel
On Thu, Apr 10, 2014 at 9:44 AM, Andrew Ayre wrote:
> Hi,
>
>
Hi,
This workaround is working well, but will there be a fix to IronPython
so it isn't needed?
I need to give feedback to the SymPy people.
Thanks! Andy
On 4/9/2014 10:02 AM, Pawel Jasinski wrote:
> Here is the workaround which let me install the package:
>
> *** sympy/__init__.py.orig 20
comment the following line out in sympy/__init__.py
from .core import *
but, I can see already another import error.
--pawel
On Wed, Apr 9, 2014 at 10:07 AM, Andrew Ayre wrote:
> OK. Is there a workaround I can use?
>
> Andy
>
> On 4/8/2014 8:04 PM, Pawel Jasinski wrote:
>> It looks like the im
OK. Is there a workaround I can use?
Andy
On 4/8/2014 8:04 PM, Pawel Jasinski wrote:
> It looks like the import bug, but is different.
> This time imported is confusing already imported: sympy.core.sets
> with sympy.sets. Is is looking for sympy.sets.fancysets in sympty.core.sets
>
> On Tue, A
On 4/8/2014 10:28 AM, Jeff Hardy wrote:
> On Tue, Apr 8, 2014 at 9:08 AM, Andrew Ayre wrote:
>> Thanks. Making progress... Now it can't find sympy.sets.fancysets. I've
>> added the folder where the module is defined to sys.path:
>>
>> =
> sys.path.ap
On Tue, Apr 8, 2014 at 9:08 AM, Andrew Ayre wrote:
> Thanks. Making progress... Now it can't find sympy.sets.fancysets. I've
> added the folder where the module is defined to sys.path:
>
> =
sys.path.append('../../PythonLib/sympy/sets')
>
sys.pat
On 4/7/2014 11:32 PM, Jeff Hardy wrote:
> On Mon, Apr 7, 2014 at 10:16 PM, Andrew Ayre wrote:
>> Thanks. Unfortunately I still get the error:
>>
>> =
> import sympy
>>
>> Traceback (most recent call last):
>> File "", line 1, in
>> File "C:\User
On Mon, Apr 7, 2014 at 10:16 PM, Andrew Ayre wrote:
> Thanks. Unfortunately I still get the error:
>
> =
import sympy
>
> Traceback (most recent call last):
> File "", line 1, in
> File "C:\Users\Andy\Documents\ADScript\PythonLib\sympy\__init__.
Thanks. Unfortunately I still get the error:
=
>>>import sympy
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Andy\Documents\ADScript\PythonLib\sympy\__init__.py",
line 32, in
File
"C:\Users\Andy\Documents\ADScript\PythonL
this looks like https://ironpython.codeplex.com/workitem/34551 which
is fixed post 2.7.4.
Can you try 2.7.5b1 https://ironpython.codeplex.com/releases/view/115611 ?
On Mon, Apr 7, 2014 at 12:03 PM, Andrew Ayre wrote:
> Hello,
>
> I have embedded IronPython 2.7.4 into a .NET 4.0 C# application. I
Hi,
I was all excited for a moment... until I realized that there are two
projects called SymPy(!).
The one I am trying to use is currently at 0.7.5 and is for symbolic
computation:
http://sympy.org/en/index.html
:(
Andreas - thanks for replying, I appreciate it.
Andy
On 4/7/2014 12:58 PM, A
Hi,
I've not had problems running SimPy samples with IronPython. In fact, I
copied the MachineShop sample from their page and added it to a Python
project in VS2013 (you need to have PythonTools for Visual Studio installed
to do this). I could run that Python project without problems. I also ran
t
15 matches
Mail list logo