As long as I can still download Python.NET for Python 2.7, I don't care
about future development.
My use case is a legacy Python 2.7 application that works with a data
acquisition system that has .NET drivers. I'm not currently developing it,
but we are still actively using it.
On Thu, Jun 13, 20
We used Python.NET several years ago to write Python scripts that can
interface with data acquisition systems from Measurement Computing
(formerly Data Translation). These boards have an OpenLayers driver library
in .NET; they don't have any native Python drivers. Using Python.NET as a
bridge was f
Is there a way to trap errors in python.net? I have an instance of
try:
doSomethingInDotNetThatMayFail()
except:
logger.exception("Something really wrong happened")
and when the .NET library I'm using fails, it prints out an error message
but never gets to the except: clause, and
Never mind, I figured it out, you just have to make sure the .dll files are
in the PYTHONPATH.
On Tue, Jul 23, 2013 at 1:45 PM, Jason Sachs wrote:
> I got the pythonnet libraries installed and working with my Python
> installation, and I can do
>
> import clr
> import Sys
I got the pythonnet libraries installed and working with my Python
installation, and I can do
import clr
import System
without errors, but when I go to import a 3rd-party .NET library I have
installed, it can't find it:
>>> import clr
>>> import System
>>> import OpenLayers.Base
Traceback (m
thanks both of you!
On Tue, Jul 23, 2013 at 8:39 AM, Daniel Krause wrote:
> This link might help you:
> http://www.lfd.uci.edu/~gohlke/pythonlibs/
>
>
> 2013/7/23 Jason Sachs
>
>> is there a prebuilt version of pythonnet for x64? I tried downloading
>> source +
, or some other
> binary incompatibility.
>
> On Jul 22, 2013, at 7:54 PM, Jason Sachs wrote:
>
> ...yet when I run npython.exe it works fine:
>
> C:\>c:\app\python\anaconda\1.6.0\lib\site-packages\pythonnet\npython
> Python 2.7.5 |Anaconda 1.6.0 (64-bit)| (default, Ma
or "license" for more information.
>>> import System
>>>
On Mon, Jul 22, 2013 at 4:53 PM, Jason Sachs wrote:
> I'm still missing this. Here's what I tried (never mind Eclipse+pydev for
> the moment, I'm just trying to run a python.exe to get what I
M, Bradley Friedman wrote:
> You may be able to drop the binaries into those locations. Note I said
> build/acquire. In that case you'd acquire.
>
> Deployment is another matter.
>
> When it comes to PyDev, you'll want to make sure it's using the PYTHONPATH
> and
of ways to do this. depending on what you are downloading or building and
> where you are deploying.
>
> You will likely need to better define your ultimate deployment
> requirements/needs to figure out how you'd want to approach that issue.
>
> -brad
>
> On Jul 22, 2013,
Hi there--
I've used Python a lot but am new to pythondotnet. I got it running on
Windows 7 with no problem, by unzipping the download file, making sure
PYTHONPATH and PYTHONHOME were setup properly, and running npython.exe.
How do you get it to run in a debugger? (either PyDev on Eclipse, or
Mic
11 matches
Mail list logo
