Yes, you can set the PYTHONHOME variable from .net prior to calling
the initialize. Many of the python runtimes set registry keys or are
located in default locations.
mike
On 6/6/07, Barrett, Joey <[EMAIL PROTECTED]> wrote:
>
> Thank you for your response, this is helpful.
>
> The methods called
If anyone out there has any known issues/bugs please enter them into the bug
database on sourceforge so they can be tracked and fixed.
When possible please include sample source code and information on os and .net
version.
Thanks!
mike
_
Python.NE
The unofficial version of Python.NET for .NET Framework v2.0 has been
updated and available for download in both pre-compiled or source
form. Please not the source form will require the installation of the
Visual Studio 2005 SDK (~125MB download), and Visual IL.
This release incorporates some bug
Good to see some feedback, comments inlined. Should see a new post
of my 2.0 release with some fixes today including just a binary
release.
On 2/20/06, T Barket <[EMAIL PROTECTED]> wrote:
> Hello,
>
> 1) the PythonNet2.0-0.1.zip file didn't include a file called "clrmodule.il"
> but I substitut
Hey all,
I've made my Python.NET v2.0 code available if anyone wants to take a
peek at it. Requires Visual Studio 2005 Beta 2 or newer to compile
along with the Visual IL add-in.
http://sourceforge.net/project/showfiles.php?group_id=149840
mike
_
Been playing around with RunString implementations looking for what
works best. Here is my result. I am able to run any python script
loaded from file just fine. Also, between calls to RunString local
variables are saved just fine.
protected static PyDict locals = null;
public
Did a
search/replace and whala.
mike
On 9/19/05, Greg Chapman <[EMAIL PROTECTED]> wrote:
> Michael Eddington wrote:
>
> > Anyone else out there started to mess with Python.NET on the 2.0
> > platform? One of the first hurtles was the output from ildasm does
> > not alway
Anyone else out there started to mess with Python.NET on the 2.0
platform? One of the first hurtles was the output from ildasm does
not always place the method name on the next line, causing
callconvutil to place the modopt in the wrong place. I've added a
regex in to check for and split the meth
Anyone else out there started to mess with Python.NET on the 2.0
platform? One of the first hurtles was the output from ildasm does
not always place the method name on the next line, causing
callconvutil to place the modopt in the wrong place. I've added a
regex in to check for and split the meth
Anyone else out there started to mess with Python.NET on the 2.0
platform? One of the first hurtles was the output from ildasm
does not always place the method name on the next line, causing
callconvutil to place the modopt in the wrong place. I've added a
regex in to check for and split the meth
"Ported" the makefile to nmake (attached).
mike
# Makefile for the PythonRuntime .NET assembly and tests. Thanks to
# Camilo Uribe <[EMAIL PROTECTED]> for contributing Mono support.
RELEASE=pythonnet-1.0-rc2-py2.4-clr1.1-src
RUNNER=
ILDASM=ildasm
ILASM=ilasm
CSC=csc.exe
all: python.exe CLR.dll
l to return anything meaningful, so you have
>to build the locals dict manually.
>
>HTH,
>
>
>Brian Lloyd[EMAIL PROTECTED]
>V.P. Engineering 540.361.1716
>Zope Corporation http://www.zope.com
>
>
>
>
>>-Original Messa
I would like to run Python strings and get an object return from .NET.
To this end I added PyRun_String to the Runtime object and another
method to PythonEngine ala the existing SimpleString implementation.
Everything compiles, but Runtime.PyRun_String always returns a NULL,
and it does not look
13 matches
Mail list logo
