From aklein at bluemountaincapital.com Wed Jun 4 01:01:59 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Tue, 3 Jun 2014 23:01:59 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Message-ID: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From btribble at ea.com Wed Jun 4 01:15:36 2014 From: btribble at ea.com (Tribble, Brett) Date: Tue, 3 Jun 2014 23:15:36 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> Message-ID: 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad at fie.us Wed Jun 4 04:48:30 2014 From: brad at fie.us (Bradley Friedman) Date: Tue, 3 Jun 2014 22:48:30 -0400 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> Message-ID: <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> 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 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 at python.org] On Behalf Of Adam Klein > Sent: Tuesday, June 03, 2014 4:02 PM > To: pythondotnet at 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 mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at pyxll.com Wed Jun 4 12:15:23 2014 From: tony at pyxll.com (Tony Roberts) Date: Wed, 4 Jun 2014 11:15:23 +0100 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> Message-ID: 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 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 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 at python.org > ] *On Behalf Of *Adam > Klein > *Sent:* Tuesday, June 03, 2014 4:02 PM > *To:* pythondotnet at 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 mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > > > > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aklein at bluemountaincapital.com Wed Jun 4 01:23:17 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Tue, 3 Jun 2014 23:23:17 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> Message-ID: <60CDCA83B420BB48BF95B8AF66CE7FFF21929485@NYMBX02.bcna.corp> I think I found one problem ... in FindAssembly (in assemblymanager.cs), the name it passes for assembly dependencies seems to be of the following form: "c:\\path\\Assembly, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null" It therefore fails to find the assembly... From: PythonDotNet [mailto:pythondotnet-bounces+aklein=bmcm.com at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 7:02 PM To: pythondotnet at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aklein at bluemountaincapital.com Wed Jun 4 01:28:33 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Tue, 3 Jun 2014 23:28:33 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> Message-ID: <60CDCA83B420BB48BF95B8AF66CE7FFF21929499@NYMBX02.bcna.corp> Confirmed that commit b65fa30c7b21cce263ed9ada982bd47bc18eea04 Use Assembly.Load(Byte[]) instead of Assembly.LoadFrom. leads to the behavior below for me ... and prior to that, things work. Any suggestions would be welcome. From: Adam Klein Sent: Tuesday, June 03, 2014 7:23 PM To: pythondotnet at python.org Subject: RE: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet I think I found one problem ... in FindAssembly (in assemblymanager.cs), the name it passes for assembly dependencies seems to be of the following form: "c:\\path\\Assembly, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null" It therefore fails to find the assembly... From: PythonDotNet [mailto:pythondotnet-bounces+aklein=bmcm.com at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 7:02 PM To: pythondotnet at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aklein at bluemountaincapital.com Wed Jun 4 02:05:30 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Wed, 4 Jun 2014 00:05:30 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp>, Message-ID: <4B1E5D2F-78E0-4073-B7F3-B5267C11B21B@bluemountaincapital.com> Right, so the assembly is indeed found in the pythonpath, but other assemblies it depends on transitively (in the same directory) are not loaded as a result of the malformation of the path + name string ... On Jun 3, 2014, at 7:48 PM, "Tribble, Brett" > 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From aklein at bluemountaincapital.com Wed Jun 4 14:54:46 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Wed, 4 Jun 2014 12:54:46 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> Message-ID: <60CDCA83B420BB48BF95B8AF66CE7FFF2192A914@NYMBX02.bcna.corp> 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 at 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 > 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 > 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From aklein at bluemountaincapital.com Wed Jun 4 16:18:06 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Wed, 4 Jun 2014 14:18:06 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> Message-ID: <60CDCA83B420BB48BF95B8AF66CE7FFF2192AA8E@NYMBX02.bcna.corp> 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 at 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 > 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 > 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From aklein at bluemountaincapital.com Wed Jun 4 16:20:42 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Wed, 4 Jun 2014 14:20:42 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Message-ID: <60CDCA83B420BB48BF95B8AF66CE7FFF2192AAA0@NYMBX02.bcna.corp> 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 at 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 > 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 > 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad at fie.us Wed Jun 4 18:48:39 2014 From: brad at fie.us (Brad Friedman) Date: Wed, 4 Jun 2014 12:48:39 -0400 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> Message-ID: <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> Umm. As an asside: seriously? You are only supporting setup.py builds from this branch? That's a problem. Python.net is also used to embed python. Therefore, it should build from IDE on all platforms and also from an autotools system. > On Jun 4, 2014, at 6:15 AM, Tony Roberts wrote: > > 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 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 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 at python.org] On Behalf Of Adam Klein >>> Sent: Tuesday, June 03, 2014 4:02 PM >>> To: pythondotnet at 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 mailing list - PythonDotNet at python.org >>> https://mail.python.org/mailman/listinfo/pythondotnet >> >> >> _________________________________________________ >> Python.NET mailing list - PythonDotNet at python.org >> https://mail.python.org/mailman/listinfo/pythondotnet > > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthoff at berkeley.edu Wed Jun 4 19:46:19 2014 From: anthoff at berkeley.edu (David Anthoff) Date: Wed, 4 Jun 2014 10:46:19 -0700 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> Message-ID: Pull requests to fix this are more than welcome :) I agree that building from the IDE should also work, but right now there doesn?t seem to be the man power to fix all of these things. From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Brad Friedman Sent: Wednesday, June 4, 2014 9:49 AM To: A list for users and developers of Python for .NET Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Umm. As an asside: seriously? You are only supporting setup.py builds from this branch? That's a problem. Python.net is also used to embed python. Therefore, it should build from IDE on all platforms and also from an autotools system. On Jun 4, 2014, at 6:15 AM, Tony Roberts > wrote: 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 > 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 > 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad at fie.us Wed Jun 4 20:35:45 2014 From: brad at fie.us (Bradley Friedman) Date: Wed, 4 Jun 2014 14:35:45 -0400 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> Message-ID: Yes. But the problem is: before the migration, those things DID work. And it was the pip/setup.py that needed to be fixed up. It sounds like you?re saying you?ve sacrificed all of it just to get a pip install working for windows. This is extremely troubling. I have not looked at the git branch yet. But now I need to investigate what exactly is going on. On Jun 4, 2014, at 1:46 PM, David Anthoff wrote: > Pull requests to fix this are more than welcome :) I agree that building from the IDE should also work, but right now there doesn?t seem to be the man power to fix all of these things. > > From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Brad Friedman > Sent: Wednesday, June 4, 2014 9:49 AM > To: A list for users and developers of Python for .NET > Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet > > Umm. As an asside: seriously? You are only supporting setup.py builds from this branch? That's a problem. Python.net is also used to embed python. Therefore, it should build from IDE on all platforms and also from an autotools system. > > On Jun 4, 2014, at 6:15 AM, Tony Roberts wrote: > > 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 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 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 at python.org] On Behalf Of Adam Klein > Sent: Tuesday, June 03, 2014 4:02 PM > To: pythondotnet at 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 mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > > > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthoff at berkeley.edu Wed Jun 4 21:38:18 2014 From: anthoff at berkeley.edu (David Anthoff) Date: Wed, 4 Jun 2014 12:38:18 -0700 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> Message-ID: Ok, actually we are talking past each other. The problem Adam had apparently has nothing to do with the migration or the pip stuff, it probably is just caused by a bug introduced in a recent commit, the code Adam identified. We should fix that once we have figured out all the details. As far as I can tell building from VS still works, none of the changes made should cause a problem for that. If they did, we should fix them, but so far I am not aware of anything that broke building from VS. I also want to stress that what we have on github right now is not a released version. We are slowly working towards a release. If you find bugs or regressions in the prerelease version, please help us to fix them. The best way to make sure things work in your environment is to test and help out. From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Bradley Friedman Sent: Wednesday, June 4, 2014 11:36 AM To: pythondotnet at python.org Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Yes. But the problem is: before the migration, those things DID work. And it was the pip/setup.py that needed to be fixed up. It sounds like you're saying you've sacrificed all of it just to get a pip install working for windows. This is extremely troubling. I have not looked at the git branch yet. But now I need to investigate what exactly is going on. On Jun 4, 2014, at 1:46 PM, David Anthoff > wrote: Pull requests to fix this are more than welcome :) I agree that building from the IDE should also work, but right now there doesn't seem to be the man power to fix all of these things. From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Brad Friedman Sent: Wednesday, June 4, 2014 9:49 AM To: A list for users and developers of Python for .NET Subject: Re: [Python.NET ] homebrew pythonnet, versus pip install --pre pythonnet Umm. As an asside: seriously? You are only supporting setup.py builds from this branch? That's a problem. Python.net is also used to embed python. Therefore, it should build from IDE on all platforms and also from an autotools system. On Jun 4, 2014, at 6:15 AM, Tony Roberts < tony at pyxll.com> wrote: 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 at 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 at 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at pyxll.com Thu Jun 5 00:44:56 2014 From: tony at pyxll.com (Tony Roberts) Date: Wed, 4 Jun 2014 23:44:56 +0100 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> Message-ID: The projects/solutions still work the same as they did before, but I always found the different targets a bit hit and miss as to how consistently they were set up. Setup.py builds using msbuild and (more or less) the same solution file that was there previously. You can still load it into visual studio. Setup.py sets some build options according to the version of python being used. I suggested using setup.py as that's what I consider the most reliable/reproducible method. You don't need to build it in an IDE in order to embed python. You should be able to just add a reference to the assembly built as part of the setup.py build. On Wednesday, June 4, 2014, Bradley Friedman wrote: > Yes. But the problem is: before the migration, those things DID work. > And it was the pip/setup.py that needed to be fixed up. It sounds like > you?re saying you?ve sacrificed all of it just to get a pip install working > for windows. This is extremely troubling. I have not looked at the git > branch yet. But now I need to investigate what exactly is going on. > > > On Jun 4, 2014, at 1:46 PM, David Anthoff > wrote: > > Pull requests to fix this are more than welcome :) I agree that building > from the IDE should also work, but right now there doesn?t seem to be the > man power to fix all of these things. > > *From:* PythonDotNet [ > mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org > > ] *On Behalf Of *Brad Friedman > *Sent:* Wednesday, June 4, 2014 9:49 AM > *To:* A list for users and developers of Python for .NET > *Subject:* Re: [Python.NET] homebrew pythonnet, versus pip install --pre > pythonnet > > Umm. As an asside: seriously? You are only supporting setup.py builds > from this branch? That's a problem. Python.net is > also used to embed python. Therefore, it should build from IDE on all > platforms and also from an autotools system. > > > On Jun 4, 2014, at 6:15 AM, Tony Roberts wrote: > > 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 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 wrote: > > > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > > https://mail.python.org/mailman/listinfo/pythondotnet > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aklein at bluemountaincapital.com Wed Jun 4 23:17:48 2014 From: aklein at bluemountaincapital.com (Adam Klein) Date: Wed, 4 Jun 2014 21:17:48 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> Message-ID: <60CDCA83B420BB48BF95B8AF66CE7FFF2192BA84@NYMBX02.bcna.corp> Agreed - had no problem building in VS. I did have some problems in setup.py, that I pointed out (but only having to do with my registry keys not aligning with what the script expected). I'm learning a lot from the source code, and the way it "just works" from cpython really is mind blowing. Kudos once again. From: PythonDotNet [mailto:pythondotnet-bounces+aklein=bmcm.com at python.org] On Behalf Of David Anthoff Sent: Wednesday, June 04, 2014 3:38 PM To: 'A list for users and developers of Python for .NET' Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Ok, actually we are talking past each other. The problem Adam had apparently has nothing to do with the migration or the pip stuff, it probably is just caused by a bug introduced in a recent commit, the code Adam identified. We should fix that once we have figured out all the details. As far as I can tell building from VS still works, none of the changes made should cause a problem for that. If they did, we should fix them, but so far I am not aware of anything that broke building from VS. I also want to stress that what we have on github right now is not a released version. We are slowly working towards a release. If you find bugs or regressions in the prerelease version, please help us to fix them. The best way to make sure things work in your environment is to test and help out. From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Bradley Friedman Sent: Wednesday, June 4, 2014 11:36 AM To: pythondotnet at python.org Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Yes. But the problem is: before the migration, those things DID work. And it was the pip/setup.py that needed to be fixed up. It sounds like you're saying you've sacrificed all of it just to get a pip install working for windows. This is extremely troubling. I have not looked at the git branch yet. But now I need to investigate what exactly is going on. On Jun 4, 2014, at 1:46 PM, David Anthoff > wrote: Pull requests to fix this are more than welcome :) I agree that building from the IDE should also work, but right now there doesn't seem to be the man power to fix all of these things. From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Brad Friedman Sent: Wednesday, June 4, 2014 9:49 AM To: A list for users and developers of Python for .NET Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Umm. As an asside: seriously? You are only supporting setup.py builds from this branch? That's a problem. Python.net is also used to embed python. Therefore, it should build from IDE on all platforms and also from an autotools system. On Jun 4, 2014, at 6:15 AM, Tony Roberts > wrote: 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 > 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 > 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgill at tokiomillennium.com Wed Jun 11 20:35:24 2014 From: jgill at tokiomillennium.com (John Gill) Date: Wed, 11 Jun 2014 18:35:24 +0000 Subject: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet In-Reply-To: <60CDCA83B420BB48BF95B8AF66CE7FFF2192BA84@NYMBX02.bcna.corp> References: <60CDCA83B420BB48BF95B8AF66CE7FFF2192945E@NYMBX02.bcna.corp> <227B8D97-7D87-4240-B2BC-EBD8F56A3FB7@fie.us> <80429076-8132-4477-93F3-6DF8FF8445E5@fie.us> <60CDCA83B420BB48BF95B8AF66CE7FFF2192BA84@NYMBX02.bcna.corp> Message-ID: +1 for this comment I'm learning a lot from the source code, and the way it "just works" from cpython really is mind blowing. Kudos once again. In case anyone here is interested I gave a lightning talk on python.NET at PyCon in Montreal in April: http://pyvideo.org/video/2680/lightning-talks-friday-afternoon My talk is around the 37 minute mark of the video. Thanks to everyone who made this magic possible. From: PythonDotNet [mailto:pythondotnet-bounces+jgill=tokiomillennium.com at python.org] On Behalf Of Adam Klein Sent: Wednesday, June 04, 2014 6:18 PM To: A list for users and developers of Python for .NET Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Agreed - had no problem building in VS. I did have some problems in setup.py, that I pointed out (but only having to do with my registry keys not aligning with what the script expected). I'm learning a lot from the source code, and the way it "just works" from cpython really is mind blowing. Kudos once again. From: PythonDotNet [mailto:pythondotnet-bounces+aklein=bmcm.com at python.org] On Behalf Of David Anthoff Sent: Wednesday, June 04, 2014 3:38 PM To: 'A list for users and developers of Python for .NET' Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Ok, actually we are talking past each other. The problem Adam had apparently has nothing to do with the migration or the pip stuff, it probably is just caused by a bug introduced in a recent commit, the code Adam identified. We should fix that once we have figured out all the details. As far as I can tell building from VS still works, none of the changes made should cause a problem for that. If they did, we should fix them, but so far I am not aware of anything that broke building from VS. I also want to stress that what we have on github right now is not a released version. We are slowly working towards a release. If you find bugs or regressions in the prerelease version, please help us to fix them. The best way to make sure things work in your environment is to test and help out. From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Bradley Friedman Sent: Wednesday, June 4, 2014 11:36 AM To: pythondotnet at python.org Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Yes. But the problem is: before the migration, those things DID work. And it was the pip/setup.py that needed to be fixed up. It sounds like you're saying you've sacrificed all of it just to get a pip install working for windows. This is extremely troubling. I have not looked at the git branch yet. But now I need to investigate what exactly is going on. On Jun 4, 2014, at 1:46 PM, David Anthoff > wrote: Pull requests to fix this are more than welcome :) I agree that building from the IDE should also work, but right now there doesn't seem to be the man power to fix all of these things. From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Brad Friedman Sent: Wednesday, June 4, 2014 9:49 AM To: A list for users and developers of Python for .NET Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet Umm. As an asside: seriously? You are only supporting setup.py builds from this branch? That's a problem. Python.net is also used to embed python. Therefore, it should build from IDE on all platforms and also from an autotools system. On Jun 4, 2014, at 6:15 AM, Tony Roberts > wrote: 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 > 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 > 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 at python.org] On Behalf Of Adam Klein Sent: Tuesday, June 03, 2014 4:02 PM To: pythondotnet at 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 mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet This communication and any attachments contain information which is confidential and may also be legally privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of disclosure, distribution, copying, printing or use of this communication or the information in it or in any attachments is strictly prohibited and may be unlawful. If you have received this communication in error, please return it with the title "received in error" to postmaster at tokiomillennium.com and then permanently delete the email and any attachments from your system. E-mail communications cannot be guaranteed to be secure or error free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. It is the recipient's responsibility to ensure that e-mail transmissions and any attachments are virus free. We do not accept liability for any damages or other consequences caused by information that is intercepted, corrupted, amended, lost, destroyed, arrives late or incomplete or contains viruses. ****************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From beckettsimmons at hotmail.com Fri Jun 13 18:18:12 2014 From: beckettsimmons at hotmail.com (Beckett Simmons) Date: Fri, 13 Jun 2014 16:18:12 +0000 Subject: [Python.NET] Python 3.4 Support Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at pyxll.com Fri Jun 13 19:42:32 2014 From: tony at pyxll.com (Tony Roberts) Date: Fri, 13 Jun 2014 18:42:32 +0100 Subject: [Python.NET] Python 3.4 Support In-Reply-To: References: Message-ID: 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 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 at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sudharshan.Munikenchaiah at in.bosch.com Fri Jun 13 07:42:46 2014 From: Sudharshan.Munikenchaiah at in.bosch.com (Sudharshan Munikenchaiah (RBEI/ETB3)) Date: Fri, 13 Jun 2014 13:42:46 +0800 Subject: [Python.NET] Re: [matplotlib-devel] .NET backend working Message-ID: <3F547BC6897EBB4BA9E98FCFDCBB4DF30258D343C2@SGPMBX06.APAC.bosch.com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandre.pineau.p at free.fr Mon Jun 16 10:07:14 2014 From: alexandre.pineau.p at free.fr (alexandre.pineau.p at free.fr) Date: Mon, 16 Jun 2014 10:07:14 +0200 (CEST) Subject: [Python.NET] using external assembly with pythonnet In-Reply-To: <1893138842.8791798.1402902432129.JavaMail.root@zimbra33-e6.priv.proxad.net> Message-ID: <1214306316.8997413.1402906034846.JavaMail.root@zimbra33-e6.priv.proxad.net> 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthoff at berkeley.edu Mon Jun 16 17:42:53 2014 From: anthoff at berkeley.edu (David Anthoff) Date: Mon, 16 Jun 2014 08:42:53 -0700 Subject: [Python.NET] [matplotlib-devel] .NET backend working In-Reply-To: <3F547BC6897EBB4BA9E98FCFDCBB4DF30258D343C2@SGPMBX06.APAC.bosch.com> References: <3F547BC6897EBB4BA9E98FCFDCBB4DF30258D343C2@SGPMBX06.APAC.bosch.com> Message-ID: Hi Sudharshan, Python.Net has nothing to do with IronPython, so this is probably not the right place to find info on IronPython solutions. I was looking for the same thing as you a couple of years ago and didn't find anything. For a time there were some efforts to bring the scientific python stack over to IronPython, but that effort apparently has stopped entirely, as far as I can tell. You might be better of using Python.Net (what this mailing list is about): it allows you to run normal CPython, but call .Net code pretty seamlessly from your python code. In that setup you can of course use any of the normal plotting libraries that are available for python. Best, David From: PythonDotNet [mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org] On Behalf Of Sudharshan Munikenchaiah (RBEI/ETB3) Sent: Thursday, June 12, 2014 10:43 PM To: pythondotnet at python.org Subject: [Python.NET] Re: [matplotlib-devel] .NET backend working 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From beckettsimmons at hotmail.com Tue Jun 17 21:47:36 2014 From: beckettsimmons at hotmail.com (Beckett Simmons) Date: Tue, 17 Jun 2014 19:47:36 +0000 Subject: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 In-Reply-To: References: Message-ID: 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 > To: "A list for users and developers of Python for .NET" > > Subject: Re: [Python.NET] Python 3.4 Support > Message-ID: > > 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 > 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 at python.org > > https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at pyxll.com Tue Jun 17 23:58:21 2014 From: tony at pyxll.com (Tony Roberts) Date: Tue, 17 Jun 2014 22:58:21 +0100 Subject: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 In-Reply-To: References: Message-ID: 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 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 > > > To: "A list for users and developers of Python for .NET" > > > > > Subject: Re: [Python.NET] Python 3.4 Support > > Message-ID: > > > > > > 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 at 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 at python.org > > > > https://mail.python.org/mailman/listinfo/pythondotnet > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From beckettsimmons at hotmail.com Wed Jun 18 19:17:14 2014 From: beckettsimmons at hotmail.com (Beckett Simmons) Date: Wed, 18 Jun 2014 17:17:14 +0000 Subject: [Python.NET] Python 3.4 Support In-Reply-To: References: Message-ID: 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 > To: "A list for users and developers of Python for .NET" > > Subject: Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 > Message-ID: > > 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 > 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 > > > > > To: "A list for users and developers of Python for .NET" > > > > > > > > Subject: Re: [Python.NET] Python 3.4 Support > > > Message-ID: > > > > > > > > > > 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 at 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 at python.org > > > > > > https://mail.python.org/mailman/listinfo/pythondotnet > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at pyxll.com Wed Jun 18 20:30:30 2014 From: tony at pyxll.com (Tony Roberts) Date: Wed, 18 Jun 2014 19:30:30 +0100 Subject: [Python.NET] Python 3.4 Support In-Reply-To: References: Message-ID: 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 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 > > > To: "A list for users and developers of Python for .NET" > > > > > Subject: Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 > > Message-ID: > > > > > 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 > > > 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 > > > ');>> > > > > To: "A list for users and developers of Python for .NET" > > > > > > > ');>> > > > > Subject: Re: [Python.NET] Python 3.4 Support > > > > Message-ID: > > > > > > > CA%2BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q at 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 at 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 at python.org > > > > ');> > > > > > https://mail.python.org/mailman/listinfo/pythondotnet > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cgohlke at uci.edu Wed Jun 18 20:10:24 2014 From: cgohlke at uci.edu (Christoph Gohlke) Date: Wed, 18 Jun 2014 11:10:24 -0700 Subject: [Python.NET] Python 3.4 Support In-Reply-To: References: Message-ID: <53A1D610.2000201@uci.edu> Hi, I updated the installers at Christoph On 6/18/2014 10:17 AM, Beckett Simmons 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 >> To: "A list for users and developers of Python for .NET" >> >> Subject: Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 >> Message-ID: >> >> 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 >> 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 > > > >> > > To: "A list for users and developers of Python for .NET" >> > > > > > >> > > Subject: Re: [Python.NET] Python 3.4 Support >> > > Message-ID: >> > > > > >> > > >> > > 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 at 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 at python.org >> > >> > > > https://mail.python.org/mailman/listinfo/pythondotnet >> > >> > > > > > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > From beckettsimmons at hotmail.com Wed Jun 18 21:38:24 2014 From: beckettsimmons at hotmail.com (Beckett Simmons) Date: Wed, 18 Jun 2014 19:38:24 +0000 Subject: [Python.NET] PythonDotNet Digest, Vol 122, Issue 17 In-Reply-To: References: Message-ID: 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 > To: "A list for users and developers of Python for .NET" > > Subject: Re: [Python.NET] Python 3.4 Support > Message-ID: > > 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 > 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 > > > > > To: "A list for users and developers of Python for .NET" > > > > > > > > Subject: Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 > > > Message-ID: > > > > > > > > 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 > > > > > 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 > > > > > > ');>> > > > > > To: "A list for users and developers of Python for .NET" > > > > > > > > > > > ');>> > > > > > Subject: Re: [Python.NET] Python 3.4 Support > > > > > Message-ID: > > > > > > > > > > > CA%2BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q at 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 at 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 at python.org > > > > > > > ');> > > > > > > https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at pyxll.com Thu Jun 19 10:25:10 2014 From: tony at pyxll.com (Tony Roberts) Date: Thu, 19 Jun 2014 09:25:10 +0100 Subject: [Python.NET] PythonDotNet Digest, Vol 122, Issue 17 In-Reply-To: References: Message-ID: Hi Becket, you just need to uninstall/delete the pythonnet egg you have installed. When it was installed as an egg it would have been added to your easy-install.pth file in site-packages, and so that egg is being picked up before the new version even though the new version is on the python path. Deleting the old egg folder is the easier way to ensure it doesn't get imported by mistake. If you want to install your build into your virtualenv you can use the 'install' distutils command: >> python setupwin.py install Or you can build an egg using 'setupegg.py' and install it that way (which is convenient as it installs it in its own sub-folder in site-packages so is easier to completely uninstall later): >> python setupegg.py bdist_egg >> easy_install dist\pythonnet..egg The setup.py in the main repo is cleaner, and we will eventually get the python3 changes merged into that :) cheers, Tony On Wed, Jun 18, 2014 at 8:38 PM, Beckett Simmons wrote: > 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 > > To: "A list for users and developers of Python for .NET" > > > > Subject: Re: [Python.NET] Python 3.4 Support > > Message-ID: > > > > 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 > > > 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 > > > > > > > To: "A list for users and developers of Python for .NET" > > > > > > > > > > > Subject: Re: [Python.NET] PythonDotNet Digest, Vol 122, Issue 13 > > > > Message-ID: > > > > > > > > > > > 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 at 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 > > > > > > > > > ');>> > > > > > > To: "A list for users and developers of Python for .NET" > > > > > > > > > > > > > > > ');>> > > > > > > Subject: Re: [Python.NET] Python 3.4 Support > > > > > > Message-ID: > > > > > > < > CA+XbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q at mail.gmail.com > > > CA%2BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q at mail.gmail.com');> > > > > > > > CA%2BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q at mail.gmail.com > > > CA%252BXbcsbgTfLdGOaLPNHqMTrgyOvRYSULD9T_cJZK0t78ocAG-Q at 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 at 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 at python.org > > > > > > > > > > ');> > > > > > > > https://mail.python.org/mailman/listinfo/pythondotnet > > _________________________________________________ > Python.NET mailing list - PythonDotNet at python.org > https://mail.python.org/mailman/listinfo/pythondotnet > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandre.pineau.p at free.fr Thu Jun 19 09:59:11 2014 From: alexandre.pineau.p at free.fr (alexandre.pineau.p at free.fr) Date: Thu, 19 Jun 2014 09:59:11 +0200 (CEST) Subject: [Python.NET] using external assembly with pythonnet In-Reply-To: <1214306316.8997413.1402906034846.JavaMail.root@zimbra33-e6.priv.proxad.net> Message-ID: <1394555285.878843.1403164751591.JavaMail.root@zimbra33-e6.priv.proxad.net> Additional information : I have done this test on Windows Xp 32. I will soon be able to try on Windows 7 64 bits. Do you know where I can find exemples of call if external assembly with pythonnet ? Thanks for your help, Alexandre ----- Mail original ----- De: "alexandre pineau p" ?: pythondotnet at python.org Envoy?: Lundi 16 Juin 2014 10:07:14 Objet: [Python.NET] using external assembly with pythonnet 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 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 _________________________________________________ Python.NET mailing list - PythonDotNet at python.org https://mail.python.org/mailman/listinfo/pythondotnet -------------- next part -------------- An HTML attachment was scrubbed... URL: From kalman_g at verizon.net Thu Jun 26 23:49:15 2014 From: kalman_g at verizon.net (GKalman) Date: Thu, 26 Jun 2014 14:49:15 -0700 (PDT) Subject: [Python.NET] Modifying List of Lists Message-ID: <1403819355949-5062231.post@n6.nabble.com> """ 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. From kalman_g at verizon.net Fri Jun 27 00:07:32 2014 From: kalman_g at verizon.net (GKalman) Date: Thu, 26 Jun 2014 15:07:32 -0700 (PDT) Subject: [Python.NET] Modifying List of Lists In-Reply-To: <1403819355949-5062231.post@n6.nabble.com> References: <1403819355949-5062231.post@n6.nabble.com> Message-ID: <1403820452715-5062233.post@n6.nabble.com> OK testing -- View this message in context: http://python.6.x6.nabble.com/Modifying-List-of-Lists-tp5062231p5062233.html Sent from the Python - pythondotnet mailing list archive at Nabble.com.