I think this is the most popular way to do it before:
https://pytools.codeplex.com/wikipage?title=NumPy%20and%20SciPy%20for%20.Net
But this link is no longer exist:
https://store.enthought.com/repo/.iron/
I recently found a clone for the instruction, and also found a clone of ironpkg-1.0.0.py on github. But http://www.enthought.com/repo/.iron/eggs/index-depend.txt is no longer exists in the internet(I googled it, but failed to find it)
Getting started with SciPy for .NET
1.) IronPython Download and install IronPython 2.7, this will require .NET v4.0.
2.) Modify PATH
Add the install location on the path, this is usually: C:\Program File\IronPython 2.7
But on 64-bit Windows systems it is: C:\Program File (x86)\IronPython 2.7
As a check, open a Windows command prompt and go to a directory (which is not the above) and type:
ipy -V PythonContext 2.7.0.40 on .NET 4.0.30319.225
3.) ironpkg
Bootstrap ironpkg, which is a package install manager for binary (egg based) Python packages. Download ironpkg-1.0.0.py and type:
ipy ironpkg-1.0.0.py --install
Now the ironpkg command should be available:ironpkg -h (some useful help text is displayed here)
4.) scipy
Installing scipy is now easy:
ironpkg scipy numpy-2.0.0b2-1.egg
I think I have done as much as I can do. Any body succeed to install numpy and scipy for Ironpython27?
SciPy takes a somewhat conservative approach, maintaining compatibility with several major releases of Python and NumPy on the major platforms.
It is based on Python 3.4. OK, it in not 3.9, but maybe better than 2.7. One point ... it is still not possible to use the numpy and scipy with the new IronPython. I found that some people "convert" the numpy from C in C# and that it should be compatible with .
Enthought support here.
The Iron Python numpy and scipy packages can be downloaded here: http://code.enthought.com/.iron/README.txt http://code.enthought.com/.iron/eggs/index.html
FYI, Microsoft stopped work on the IronPython project in 2012 in favor of supporting standard CPython. Those archived versions of numpy and scipy were built in 2011 (so contain no newer features or fixes), and are 32-bit-only. We do not plan to update them in any way.
FYI, we typically recommend that those who wish to use Python in a .net context consider using the actively developed pythonnet package to interface with the living CPython ecosystem.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With