Thanks all for the replies! I've also been in touch with the folks at Enthought, and they provided the idea that has led to me posting a question at StackExchange: http://stackoverflow.com/questions/13222393/compiling-pythonnet-net-to-work-... I'm pretty sure my bit-to-bit issue is accounted for. I've also used the numpy from EPD in the same python I'm using for pythonnet and that has no problems. As far as the UCS issues, I was only able to build the pythonnet project as UCS-2, if I changed that string to UCS-4 the build crashed... maybe something on windows? Thanks for helping! On Sat, Nov 3, 2012 at 12:00 PM, <pythondotnet-request@python.org> wrote:
Send PythonDotNet mailing list submissions to pythondotnet@python.org
To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/pythondotnet or, via email, send a message with subject or body 'help' to pythondotnet-request@python.org
You can reach the person managing the list at pythondotnet-owner@python.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of PythonDotNet digest..."
Today's Topics:
1. Re: pythonnet and numpy (Stephen P. Lepisto) 2. Re: pythonnet and numpy (Bradley Friedman)
----------------------------------------------------------------------
Message: 1 Date: Fri, 02 Nov 2012 19:48:39 -0700 From: "Stephen P. Lepisto" <stephenp@otakuworld.com> To: pythondotnet@python.org Subject: Re: [Python.NET] pythonnet and numpy Message-ID: <50948607.3070802@otakuworld.com> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Make sure you are installing the correct "bitness" of numpy for your install of python (64-bit to 64-bit, 32-bit to 32-bit).
On 11/2/2012 8:42 AM, Bradley Friedman wrote:
That error suggests issues with your path or current directory. Multiple or incompatible dynamic libraries etc. in the path. Generally speaking, pythonnet does work with numpy. Something specific is wrong, loading a dll in a low level manner that msvc is upset.
Sent from my iPad
On Nov 2, 2012, at 10:55 AM, John Burkhart <jfburkhart.reg@gmail.com <mailto:jfburkhart.reg@gmail.com>> wrote:
Hello,
As mentioned in the other thread, I have built pythonnet with VS2012 for a 64-bit Python installation and using .NET 4 assemblies. Things seem to work well.
However, I just tried to `import numpy` and all hell broke loose... the reason I pursued pythonnet was because I thought it would allow me to use the pure CPython modules without needing to rely on any of the modified versions built for IronPython. Below is the PowerShell output from starting EPD and importing numpy and starting pythonnet python.exe and importing numpy.
PS G:\svn\Python\pythonnet\trunk\pythonnet\src\console\bin\Debug> python #should load EPD python Enthought Python Distribution -- www.enthought.com <http://www.enthought.com> Version: 7.3-2 (64-bit)
Python 2.7.3 |EPD 7.3-2 (64-bit)| (default, Apr 12 2012, 15:20:16) [MSC v.1500 64 bit (AMD64)] on win32 Type "credits", "demo" or "enthought" for more information.
import numpy; print numpy.__version__ 1.6.1 exit() PS G:\svn\Python\pythonnet\trunk\pythonnet\src\console\bin\Debug> .\python.exe Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. import numpy [Bang!] - A window opens with TITLE: Microsoft Visual C++ Runtime Library Message: Runtime Error!
Program: G:\svn\Python...
R6034 An application has made an attempt to load the C runtime library incorrectly Please contact the application's support team for more information """
This is not a lot of information, but maybe someone has some ideas on how to troubleshoot?
Thank you, john
_________________________________________________ Python.NET <http://Python.NET> mailing list - PythonDotNet@python.org <mailto:PythonDotNet@python.org> http://mail.python.org/mailman/listinfo/pythondotnet
_________________________________________________ Python.NET mailing list - PythonDotNet@python.org http://mail.python.org/mailman/listinfo/pythondotnet
-- Stephen P. Lepisto