Re: [IronPython] Parsing Stack Traces

2008-02-13 Thread Dino Viehland
Ahh, in that case the class to subclass is ErrorSink instead of CompilerSink :) Once you have an error sink you can call: ScriptEngine.Compile(source, compilerOptions, errorSink) And your sink should get notified of the errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL

Re: [IronPython] Parsing Stack Traces

2008-02-13 Thread Slide
I am using the 2.0 hosting APIs. I'll look around some more in the code. I have a situation which works now using FormatException that should work ok. thanks slide On Feb 13, 2008 2:23 PM, Dino Viehland <[EMAIL PROTECTED]> wrote: > Are you using the Python code dom provider from 1.x or directly

Re: [IronPython] Import xlrd

2008-02-13 Thread Dino Viehland
Yeah, adding Lib to sys.path will definitely also be necessary. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Machin Sent: Wednesday, February 13, 2008 12:26 PM To: Discussion of IronPython Subject: Re: [IronPython] Import xlrd Dino Viehland wrote:

Re: [IronPython] Parsing Stack Traces

2008-02-13 Thread Dino Viehland
Are you using the Python code dom provider from 1.x or directly interacting w/ the hosting APIs? I think you should get a list of errors like you'd normally get w/ CodeDom - although it'll probably only include 1 error (but it should have line info). Otherwise in 1.x you can subclass the Compi

[IronPython] ipy.exe as a Compiler

2008-02-13 Thread Pigneri, Rocco
Dear all, I am trying to use ipy.exe as a compiler to compile automatically nightly builds using a make-like build tool, and I was having some difficulty getting it to work. First, I'll lay out what I am trying to accomplish, and then lay out my questions. I want to be able to organize a large

Re: [IronPython] Import xlrd

2008-02-13 Thread John Machin
Dino Viehland wrote: > It seems like the simple answer is no – that version of IronPython is > too old and has a bug which prevents xlrd from working. The ASP.NET > Futures package may have a recent enough version that it works. > > > > Using ASP.NET futures it should be as simple as doing a

Re: [IronPython] Import xlrd

2008-02-13 Thread Dino Viehland
It seems like the simple answer is no - that version of IronPython is too old and has a bug which prevents xlrd from working. The ASP.NET Futures package may have a recent enough version that it works. Using ASP.NET futures it should be as simple as doing a sys.path.append('location_of_xlrd')

Re: [IronPython] v1.1.1: Problem loading assembly, I think

2008-02-13 Thread Dino Viehland
Does this simple case work for you? It works for me on 1.0, 1.1, and 1.1.1: Test.cs: using System; using IronPython.Hosting; public class Foo { public static void Main(string[]args) { PythonEngine pe = new PythonEngine(); EngineModule module = pe.CreateModule(); C

[IronPython] v1.1.1: Problem loading assembly, I think

2008-02-13 Thread Barry Carr
Hi, My apologies if this is really obvious but I'm stumped. The cut down python file below is called from a C# windows form app (.NET 2.0). When it runs it fails and reports: "Name 'Regex' not defined". Stepping through the python code shows that it fails as soon as comes across the first use