Mailman 3 June 2014 - Python.NET

Modifying List of Lists
by GKalman 26 Jun '14

26 Jun '14

""" Below I have two versions of a list of lists, named: RA Version #1 is "hard-wired" Version #2 is built-up from a sublist Both versions print* identical* outputs Yet if one or the other version is commented out, one get a* different* output in the modified list of lists My question is: why? """ from copy import deepcopy #Version #1: #========== RA=[[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3]] print "1a",RA,type(RA) N=3 #Version #2: #=========== RA=[] Item=[1,2,3] for i in range(N*N): RA.append(Item) print "1b",RA,type(RA) k=1 tv=1 cRA=deepcopy(RA) LL=cRA[k] print "LL before= ",LL for c in range(N): if LL[c]==tv: LL[c]=0 print "LL after= ",LL cRA[k]=LL RA=cRA #modified list of list: #=============== print "2",RA -- View this message in context: http://python.6.x6.nabble.com/Modifying-List-of-Lists-tp5062231.html Sent from the Python - pythondotnet mailing list archive at Nabble.com.

1 1

Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 17
by Beckett Simmons 19 Jun '14

19 Jun '14

Hey Tony, Following your advice I did a simple git reset and git clean to get back to the original source. Built pythonnet again. Now a weird thing is happening. I can import clr in the Mircrosoft Windows 7 x64 Debug Build Environment prompt but only immediately after the build. So I figure out that it was because I was in the pythonnet folder and that allows it to find the Python.Runtime.dll file at pythonnet\build\lib.win-amd64-3.4. I tried to to add multiple variations of that path to my system environment path. This did not work for me with any variation. What I had to do to get clr to import was to move that Python.Runtime.dll file into the H:\py341Test\Lib\site-packages\pythonnet-2.0dev-py3.4-win-amd64.egg python virtual environment. This works for me, or at least works enough to get my unit tests working. Although it doesn't seem to be the most elegant solution. Then again, I am using a third-party fork. Just wondering if you have any further pro tips about this. Again, thank you very much for your help! Beckett > Date: Wed, 18 Jun 2014 19:30:30 +0100 > From: Tony Roberts <tony(a)pyxll.com> > To: "A list for users and developers of Python for .NET" > <pythondotnet(a)python.org> > Subject: Re: [Python.NET] Python 3.4 Support > Message-ID: > <CA+Xbcsb6RUQOr+8GUzdtjWVPLRmA-vpKLmi2h2L1DhLyjBWwbA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Becket, > > hmmm, did you build it for 3.3 previously? The setupwin.py in this repo > doesn't clean before building and re-uses the same target for the different > python versions so it won't rebuild everything correctly when switching > between python versions. Try deleting all the build folders and re-build. > It's a bit rough and ready; the setup.py in the official repo works better. > > If that doesn't work let me know as I had it working ok (but I'm still > using 3.2 mostly so it hasn't had much testing). > > cheers, > Tony > > On Wednesday, June 18, 2014, Beckett Simmons <beckettsimmons(a)hotmail.com> > wrote: > > > Hey Tony, > > > > Thanks for the help. I was able to build pythonnet with your instructions. > > > > The issue that I am having now is that pythonnet seems to be build for > > python33. > > When I try to import clr I get this error and python.exe crashes. > > http://pastebin.com/0zcW6nP0 > > How would I possibly point pythonnet to the correct python34 DLL? > > > > This is what my build looks like: > > http://pastebin.com/Gb4K5PZS > > > > I would be worth while to note that I am building and running python on a > > virtual environment that comes from a python 3.4.1 64-bit base install. > > Would this possibly be the problem? > > > > Beckett > > > > > Date: Tue, 17 Jun 2014 22:58:21 +0100 > > > From: Tony Roberts <tony(a)pyxll.com > > <javascript:_e(%7B%7D,'cvml','tony(a)pyxll.com');>> > > > To: "A list for users and developers of Python for .NET" > > > <pythondotnet(a)python.org > > <javascript:_e(%7B%7D,'cvml','pythondotnet(a)python.org');>> > > > Subject: Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 > > > Message-ID: > > > <CA+XbcsbxmKF5_tRg+sVx-by-njgtmGcpzsqYbF=wno_8=ykYSQ(a)mail.gmail.com > > <javascript:_e(%7B%7D,'cvml','ykYSQ(a)mail.gmail.com');>> > > > Content-Type: text/plain; charset="utf-8" > > > > > > Hi, > > > > > > yeah it definitely does build for x64. That's what I use mostly, in fact. > > > > > > I think the 64 bit compilers don't come as part of visual studio express. > > > You can get them as part of the windows sdk download from msdn though. > > You > > > might struggle to get it to work with distutils/setup tools as they > > expect > > > the compiler to be installed as part of visual studio. What you'll need > > to > > > do is start a prompt with all the compiler stuff setup and set the env > > var > > > DISTUTILS_USE_SDK=1 to tell distutils to look at the current environment > > > for the compiler instead of the registry. > > > > > > cheers, > > > Tony > > > > > > On Tuesday, June 17, 2014, Beckett Simmons <beckettsimmons(a)hotmail.com > > <javascript:_e(%7B%7D,'cvml','beckettsimmons(a)hotmail.com');>> > > > wrote: > > > > > > > Hey Tony, > > > > > > > > Thanks for your fast reply. > > > > Your answer got setupwin.py to build for me, but only with Python 3.4 > > > > 32-bit. > > > > > > > > When I run setupwin.py with 64-bit Python I get this error: > > > > File "C:\Python341\Lib\distutils\msvc9compiler.py", line 287, in > > > > query_vcvarsall > > > > raise ValueError(str(list(result.keys()))) > > > > > > > > I am assuming that this is a compiler error because it doesn't have a > > > > 64-bit compiling function. I used the same compiler at the 32-bit build > > > > with was Visual C++ 2010 Express. And I also tried Visual Studio 2012 > > > > Express too. (Making sure to adjust my environment path accordingly.) > > > > > > > > I just want to confirm that this is indeed a compiler issue and doesn't > > > > have to do with the pythonnet code itself. > > > > > > > > Thanks, > > > > Beckett > > > > > > > > > > > > > > > > > Date: Fri, 13 Jun 2014 18:42:32 +0100 > > > > > From: Tony Roberts <tony(a)pyxll.com > > <javascript:_e(%7B%7D,'cvml','tony(a)pyxll.com');> > > > > <javascript:_e(%7B%7D,'cvml','tony(a)pyxll.com > > <javascript:_e(%7B%7D,'cvml','tony(a)pyxll.com');>');>> > > > > > To: "A list for users and developers of Python for .NET" > > > > > <pythondotnet(a)python.org > > <javascript:_e(%7B%7D,'cvml','pythondotnet(a)python.org');> > > > > <javascript:_e(%7B%7D,'cvml','pythondotnet(a)python.org > > <javascript:_e(%7B%7D,'cvml','pythondotnet(a)python.org');>');>> > > > > > Subject: Re: [Python.NET] Python 3.4 Support > > > > > Message-ID: > > > > > <CA+XbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q(a)mail.gmail.com > > <javascript:_e(%7B%7D,'cvml','CA%2BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q(a)mail.gmail.com');> > > > > <javascript:_e(%7B%7D,'cvml',' > > CA%2BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q(a)mail.gmail.com > > <javascript:_e(%7B%7D,'cvml','CA%252BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q(a)mail.gmail.com');> > > ');> > > > > > > > > > > Content-Type: text/plain; charset="utf-8" > > > > > > > > > > Hi, > > > > > > > > > > use setupwin.py instead of setup.py in the renshawbay repo to build > > it. > > > > > > > > > > cheers, > > > > > Tony > > > > > > > > > > > > > > > On Fri, Jun 13, 2014 at 5:18 PM, Beckett Simmons < > > > > beckettsimmons(a)hotmail.com > > <javascript:_e(%7B%7D,'cvml','beckettsimmons(a)hotmail.com');> > > > > <javascript:_e(%7B%7D,'cvml','beckettsimmons(a)hotmail.com > > <javascript:_e(%7B%7D,'cvml','beckettsimmons(a)hotmail.com');>');> > > > > > > wrote: > > > > > > > > > > > Hello all, > > > > > > > > > > > > I am trying to get pythonnet to build with python 3.4. I am on a > > > > Windows 7 > > > > > > 64-bit machine and specifically want to use Python 3.4.1. > > > > > > > > > > > > Of course the official repository on github does not support > > python 3.4 > > > > > > yet. > > > > > > > > > > > > I've tried this fork here: https://github.com/renshawbay/pythonnet > > > > > > But that is not working for me. Running setup.py give me this > > error: > > > > > > ValueError: close_fds is not supported on Windows platforms if you > > > > > > redirect stdin/stdout/stderr > > > > > > > > > > > > Also, checked out > > http://www.lfd.uci.edu/~gohlke/pythonlibs/#pythonnet > > > > for > > > > > > a Windows precompiled binary, but they only have the python 3.3 > > version > > > > > > there. > > > > > > > > > > > > Any other ideas or ways I could use pythonnet with Python 3.4? > > > > > > > > > > > > Beckett > > > > > > > > > > > > _________________________________________________ > > > > > > Python.NET mailing list - PythonDotNet(a)python.org > > <javascript:_e(%7B%7D,'cvml','PythonDotNet(a)python.org');> > > > > <javascript:_e(%7B%7D,'cvml','PythonDotNet(a)python.org > > <javascript:_e(%7B%7D,'cvml','PythonDotNet(a)python.org');>');> > > > > > > https://mail.python.org/mailman/listinfo/pythondotnet

2 1

using external assembly with pythonnet
by alexandre.pineau.p＠free.fr 19 Jun '14

19 Jun '14

Hello, I'm a beginner in pythonnet, and I try to use an external assembly with pythonnet. I use python 2.7.7, and a pythonnet version installed with pip install --pre pythonnet. I have also installed the framework 4 I try to load for instance the tamir dll (net version 1.1). Assembly and source available here : http://www.tamirgal.com/blog/page/SharpSSH.aspx source code : import sys sys.path.append("E:\Alex\dotnet\SharpSSH") import clr clr.AddReference("Tamir.SharpSsh" ) I obtain the following error : E:\Alex\python>testdotnet.py Traceback (most recent call last): File "E:\Alex\python\testdotnet.py", line 10, in <module> clr.AddReference("Tamir.SharpSsh") System.IO.FileNotFoundException What is wrong in my use of pythonnet ? I have checked that there is a namespace Tamir.SharpSsh in dll source files. It is also possible to load this assembly with Ctypes : windll.LoadLibrary("E:\Alex\dotnet\SharpSSH\Tamir.SharpSsh.dll") Many thanks for your help. Alexandre

1 1

Re: [Python.NET] Python 3.4 Support
by Beckett Simmons 18 Jun '14

18 Jun '14

Hey Tony, Thanks for the help. I was able to build pythonnet with your instructions. The issue that I am having now is that pythonnet seems to be build for python33.When I try to import clr I get this error and python.exe crashes.http://pastebin.com/0zcW6nP0How would I possibly point pythonnet to the correct python34 DLL? This is what my build looks like: http://pastebin.com/Gb4K5PZS I would be worth while to note that I am building and running python on a virtual environment that comes from a python 3.4.1 64-bit base install. Would this possibly be the problem? Beckett > Date: Tue, 17 Jun 2014 22:58:21 +0100 > From: Tony Roberts <tony(a)pyxll.com> > To: "A list for users and developers of Python for .NET" > <pythondotnet(a)python.org> > Subject: Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 > Message-ID: > <CA+XbcsbxmKF5_tRg+sVx-by-njgtmGcpzsqYbF=wno_8=ykYSQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > yeah it definitely does build for x64. That's what I use mostly, in fact. > > I think the 64 bit compilers don't come as part of visual studio express. > You can get them as part of the windows sdk download from msdn though. You > might struggle to get it to work with distutils/setup tools as they expect > the compiler to be installed as part of visual studio. What you'll need to > do is start a prompt with all the compiler stuff setup and set the env var > DISTUTILS_USE_SDK=1 to tell distutils to look at the current environment > for the compiler instead of the registry. > > cheers, > Tony > > On Tuesday, June 17, 2014, Beckett Simmons <beckettsimmons(a)hotmail.com> > wrote: > > > Hey Tony, > > > > Thanks for your fast reply. > > Your answer got setupwin.py to build for me, but only with Python 3.4 > > 32-bit. > > > > When I run setupwin.py with 64-bit Python I get this error: > > File "C:\Python341\Lib\distutils\msvc9compiler.py", line 287, in > > query_vcvarsall > > raise ValueError(str(list(result.keys()))) > > > > I am assuming that this is a compiler error because it doesn't have a > > 64-bit compiling function. I used the same compiler at the 32-bit build > > with was Visual C++ 2010 Express. And I also tried Visual Studio 2012 > > Express too. (Making sure to adjust my environment path accordingly.) > > > > I just want to confirm that this is indeed a compiler issue and doesn't > > have to do with the pythonnet code itself. > > > > Thanks, > > Beckett > > > > > > > > > Date: Fri, 13 Jun 2014 18:42:32 +0100 > > > From: Tony Roberts <tony(a)pyxll.com > > <javascript:_e(%7B%7D,'cvml','tony(a)pyxll.com');>> > > > To: "A list for users and developers of Python for .NET" > > > <pythondotnet(a)python.org > > <javascript:_e(%7B%7D,'cvml','pythondotnet(a)python.org');>> > > > Subject: Re: [Python.NET] Python 3.4 Support > > > Message-ID: > > > <CA+XbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q(a)mail.gmail.com > > <javascript:_e(%7B%7D,'cvml','CA%2BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q(a)mail.gmail.com');> > > > > > > Content-Type: text/plain; charset="utf-8" > > > > > > Hi, > > > > > > use setupwin.py instead of setup.py in the renshawbay repo to build it. > > > > > > cheers, > > > Tony > > > > > > > > > On Fri, Jun 13, 2014 at 5:18 PM, Beckett Simmons < > > beckettsimmons(a)hotmail.com > > <javascript:_e(%7B%7D,'cvml','beckettsimmons(a)hotmail.com');> > > > > wrote: > > > > > > > Hello all, > > > > > > > > I am trying to get pythonnet to build with python 3.4. I am on a > > Windows 7 > > > > 64-bit machine and specifically want to use Python 3.4.1. > > > > > > > > Of course the official repository on github does not support python 3.4 > > > > yet. > > > > > > > > I've tried this fork here: https://github.com/renshawbay/pythonnet > > > > But that is not working for me. Running setup.py give me this error: > > > > ValueError: close_fds is not supported on Windows platforms if you > > > > redirect stdin/stdout/stderr > > > > > > > > Also, checked out http://www.lfd.uci.edu/~gohlke/pythonlibs/#pythonnet > > for > > > > a Windows precompiled binary, but they only have the python 3.3 version > > > > there. > > > > > > > > Any other ideas or ways I could use pythonnet with Python 3.4? > > > > > > > > Beckett > > > > > > > > _________________________________________________ > > > > Python.NET mailing list - PythonDotNet(a)python.org > > <javascript:_e(%7B%7D,'cvml','PythonDotNet(a)python.org');> > > > > https://mail.python.org/mailman/listinfo/pythondotnet > > > >

3 2

Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13
by Beckett Simmons 17 Jun '14

17 Jun '14

Hey Tony, Thanks for your fast reply. Your answer got setupwin.py to build for me, but only with Python 3.4 32-bit. When I run setupwin.py with 64-bit Python I get this error: File "C:\Python341\Lib\distutils\msvc9compiler.py", line 287, in query_vcvarsall raise ValueError(str(list(result.keys()))) I am assuming that this is a compiler error because it doesn't have a 64-bit compiling function. I used the same compiler at the 32-bit build with was Visual C++ 2010 Express. And I also tried Visual Studio 2012 Express too. (Making sure to adjust my environment path accordingly.) I just want to confirm that this is indeed a compiler issue and doesn't have to do with the pythonnet code itself. Thanks, Beckett > Date: Fri, 13 Jun 2014 18:42:32 +0100 > From: Tony Roberts <tony(a)pyxll.com> > To: "A list for users and developers of Python for .NET" > <pythondotnet(a)python.org> > Subject: Re: [Python.NET] Python 3.4 Support > Message-ID: > <CA+XbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > use setupwin.py instead of setup.py in the renshawbay repo to build it. > > cheers, > Tony > > > On Fri, Jun 13, 2014 at 5:18 PM, Beckett Simmons <beckettsimmons(a)hotmail.com > > wrote: > > > Hello all, > > > > I am trying to get pythonnet to build with python 3.4. I am on a Windows 7 > > 64-bit machine and specifically want to use Python 3.4.1. > > > > Of course the official repository on github does not support python 3.4 > > yet. > > > > I've tried this fork here: https://github.com/renshawbay/pythonnet > > But that is not working for me. Running setup.py give me this error: > > ValueError: close_fds is not supported on Windows platforms if you > > redirect stdin/stdout/stderr > > > > Also, checked out http://www.lfd.uci.edu/~gohlke/pythonlibs/#pythonnet for > > a Windows precompiled binary, but they only have the python 3.3 version > > there. > > > > Any other ideas or ways I could use pythonnet with Python 3.4? > > > > Beckett > > > > _________________________________________________ > > Python.NET mailing list - PythonDotNet(a)python.org > > https://mail.python.org/mailman/listinfo/pythondotnet

2 1

Re: [matplotlib-devel] .NET backend working
by Sudharshan Munikenchaiah (RBEI/ETB3) 16 Jun '14

16 Jun '14

Hello Python team, Greetings, I am a scientific computing software developer, I am trying to migrate from matlab to C#, iron python. I have a question is there any version of matplotlib which works in ironpython or any open source graphing library for iron python . Thank You. Sudharshan Munikenchaiah(ETB3) Robert Bosch Engineering and Business Solutions Limited Engineering Solutions - Methods and Tools (RBEI/ETB3) Gold Hill Square, 690, Hosur Road, Bommanahalli, Bangalore - 566068, INDIA www.bosch.com<http://www.bosch.com>

2 1

Python 3.4 Support
by Beckett Simmons 13 Jun '14

13 Jun '14

Hello all, I am trying to get pythonnet to build with python 3.4. I am on a Windows 7 64-bit machine and specifically want to use Python 3.4.1. Of course the official repository on github does not support python 3.4 yet. I've tried this fork here: https://github.com/renshawbay/pythonnetBut that is not working for me. Running setup.py give me this error: ValueError: close_fds is not supported on Windows platforms if you redirect stdin/stdout/stderr Also, checked out http://www.lfd.uci.edu/~gohlke/pythonlibs/#pythonnet for a Windows precompiled binary, but they only have the python 3.3 version there. Any other ideas or ways I could use pythonnet with Python 3.4? Beckett

2 1

homebrew pythonnet, versus pip install --pre pythonnet
by Adam Klein 11 Jun '14

11 Jun '14

Hi All, Amazing library, first of all! I am experimenting with integrating ipython / numpy / pandas for interactive data analysis with our large existing C# codebase. We are using the Anaconda 2.0 release from ContinuumIO. With `pip install -pre pythonnet`, everything goes as expected (great!) However, when I build from source (in VS2013), point my PYTHONPATH to the clr.pyd and Python.Runtime.dll that results from the build, and run my ipython, I can do `import clr` and `ref = clr.AddReference("assemblyname")`, but I cannot load any modules within this assembly. I get a `ImportError: No module named ...` Furthermore, if I try to do ref.ExportedTypes, I get a `FileNotFoundException: Could not load file or assembly ...` where it cannot find an assembly that is referenced by the original assembly. There must be some broken loading going on... Any thoughts why this might have different behavior than what I install via PyPI (https://pypi.python.org/pypi/pythonnet/2.0.0.dev1)? Or, hints on how to debug? Thanks!!! --Adam ________________________________ This e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, the information in this e-mail by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. This communication is for informational purposes only. It is not intended as and does not constitute an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any expected returns are provided for illustrative purposes only and are not intended to serve as, and must not be relied upon by any prospective investor as, a guaranty, an assurance, a prediction of a definitive statement of fact or a probability. Investment in funds managed by BlueMountain carries certain risks, including the risk of loss of principal. Unless indicated otherwise, performance results are presented net of fees and expenses. Certain market and economic events having an impact on performance may not repeat themselves. Any comments or statements made herein do not necessarily reflect those of BlueMountain Capital Management, LLC or its affiliates. PAST PERFORMANCE IS NOT NECESSARILY INDICATIVE OF FUTURE RESULTS AND NO REPRESENTATION IS MADE THAT RESULTS SIMILAR TO THOSE SHOWN CAN BE ACHIEVED.

7 15

homebrew pythonnet, versus pip install --pre pythonnet
by Adam Klein 04 Jun '14

04 Jun '14

Sorry if this is duplicated… I’m not getting confirmation that my emails are reaching the mailing list… From: Adam Klein Sent: Wednesday, June 04, 2014 10:18 AM To: 'A list for users and developers of Python for .NET' Subject: RE: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Hopefully to save someone a headache in the future: Although I didn’t think it had anything to do with my problem, I was curious why the ‘python setup.py build_ext’ command was failing with ‘[Error 5]: Access is denied’. I put a ‘import ipdb; ipdb.set_trace()’ and found it’s because my tools/nugget/nuget.exe did not have executable permissions. Fixing that, I got a ‘RuntimeError: Windows SDK could not be found.’ This is definitely a lie - I have one installed :) Turns out my registry didn’t reflect what setup.py was trying to do. I changed keys_to_check (line 30) to include r"SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.1A\WinSDK-Win32Tools", which is where I put my InstallationFolder key set to “C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\”. Everything then compiled. For the problem I’m facing, I’ll open a GitHub issue (and try to fix myself if I can…) From: Adam Klein Sent: Wednesday, June 04, 2014 8:55 AM To: A list for users and developers of Python for .NET Subject: RE: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Sorry for not being clear – 1) I’m not building on homebrew on mac :) I am building myself using VS2013. 2) Why do I need to use the setup.py? In any case, when I do this, ie running ‘python setup.py build_ext’ command, I get a [Error 5]: Access is denied. A registry access failure perhaps? I couldn’t get this to work… 3) Everything actually works fine, my PYTHONPATH is set correctly, and it finds and loads the DLL assembly I’m trying to load. What is happening is that assembly then references other assemblies in the same path, but then, in FindAssembly (in assemblymanager.cs), the name it passes for those dependencies seems to be of the following form: "c:\\path\\XYZ, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null" It then constructs the name "c:\\path\\XYZ, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null.dll" It therefore fails to find the assembly… I confirmed that prior to the commit that changes Load(Byte[]) to LoadFrom(), everything works. That commit is b65fa30c7b21cce263ed9ada982bd47bc18eea04 Use Assembly.Load(Byte[]) instead of Assembly.LoadFrom. I can maybe fix and open a PR if I have time. But it’d be nice to confirm others see this behavior as well. From: PythonDotNet [mailto:pythondotnet-bounces+aklein=bmcm.com@python.org] On Behalf Of Tony Roberts Sent: Wednesday, June 04, 2014 6:15 AM To: A list for users and developers of Python for .NET Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Hi Adam, that 2.0.0.beta1 build was built from the source on github here: https://github.com/pythonnet/pythonnet You should build it using the setup.py script and not in the IDE. There are CI builds setup for both windows and linux (see README.md) if you want to see exactly how the wheel gets built. Best regards, Tony On Wed, Jun 4, 2014 at 3:48 AM, Bradley Friedman <brad(a)fie.us<mailto:brad@fie.us>> wrote: Can you provide the contents of the ".Config" file that is built with your particular build solution? There's a pretty good chance that the "FileNotFound" is actually mono trying to link back to Python shared libraries. Though to be honest, debugging is going to be your best bet here. You might try building in Xamarin or MonoDevelop on the mac, to be able to debug more easily. -brad On Jun 3, 2014, at 7:15 PM, Tribble, Brett <btribble(a)ea.com<mailto:btribble@ea.com>> wrote: It has been a while since I’ve had to deal with this, but make sure that your assembly is in the system path and/or pythonpath if it is not registered in the GAC. From: PythonDotNet [mailto:pythondotnet-bounces+btribble=ea.com@python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet(a)python.org<mailto:pythondotnet@python.org> Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Hi All, Amazing library, first of all! I am experimenting with integrating ipython / numpy / pandas for interactive data analysis with our large existing C# codebase. We are using the Anaconda 2.0 release from ContinuumIO. With `pip install –pre pythonnet`, everything goes as expected (great!) However, when I build from source (in VS2013), point my PYTHONPATH to the clr.pyd and Python.Runtime.dll that results from the build, and run my ipython, I can do `import clr` and `ref = clr.AddReference(“assemblyname”)`, but I cannot load any modules within this assembly. I get a `ImportError: No module named …` Furthermore, if I try to do ref.ExportedTypes, I get a `FileNotFoundException: Could not load file or assembly …` where it cannot find an assembly that is referenced by the original assembly. There must be some broken loading going on… Any thoughts why this might have different behavior than what I install via PyPI (https://pypi.python.org/pypi/pythonnet/2.0.0.dev1)? Or, hints on how to debug? Thanks!!! --Adam ________________________________ This e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, the information in this e-mail by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. This communication is for informational purposes only. It is not intended as and does not constitute an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any expected returns are provided for illustrative purposes only and are not intended to serve as, and must not be relied upon by any prospective investor as, a guaranty, an assurance, a prediction of a definitive statement of fact or a probability. Investment in funds managed by BlueMountain carries certain risks, including the risk of loss of principal. Unless indicated otherwise, performance results are presented net of fees and expenses. Certain market and economic events having an impact on performance may not repeat themselves. Any comments or statements made herein do not necessarily reflect those of BlueMountain Capital Management, LLC or its affiliates. PAST PERFORMANCE IS NOT NECESSARILY INDICATIVE OF FUTURE RESULTS AND NO REPRESENTATION IS MADE THAT RESULTS SIMILAR TO THOSE SHOWN CAN BE ACHIEVED. _________________________________________________ Python.NET<http://Python.NET> mailing list - PythonDotNet(a)python.org<mailto:PythonDotNet@python.org> https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet(a)python.org<mailto:PythonDotNet@python.org> https://mail.python.org/mailman/listinfo/pythondotnet ________________________________ This e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, the information in this e-mail by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. This communication is for informational purposes only. It is not intended as and does not constitute an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any expected returns are provided for illustrative purposes only and are not intended to serve as, and must not be relied upon by any prospective investor as, a guaranty, an assurance, a prediction of a definitive statement of fact or a probability. Investment in funds managed by BlueMountain carries certain risks, including the risk of loss of principal. Unless indicated otherwise, performance results are presented net of fees and expenses. Certain market and economic events having an impact on performance may not repeat themselves. Any comments or statements made herein do not necessarily reflect those of BlueMountain Capital Management, LLC or its affiliates. PAST PERFORMANCE IS NOT NECESSARILY INDICATIVE OF FUTURE RESULTS AND NO REPRESENTATION IS MADE THAT RESULTS SIMILAR TO THOSE SHOWN CAN BE ACHIEVED.

1 0