Re: [IronPython] Exporting Python code as an assembly (Curt Hagenlocher)

On 3/3/08, Suma Talya <[EMAIL PROTECTED]> wrote: > > Do we need to have py file also in the same directory along with dll? > Yes, that is correct. -- Curt Hagenlocher [EMAIL PROTECTED] ___ Users mailing list Users@lists.ironpython.com http://lists.ironp

Re: [IronPython] Exporting Python code as an assembly (Curt Hagenlocher)

Hi, I am having 2.0 alpha 8 of IronPython Binaries. I downloaded the wrapper changes with comment "Fixed constructor to call __init__" version no. 7386 from http://www.codeplex.com/coils/SourceControl/ListD

Re: [IronPython] Exporting Python code as an assembly

On Tue, Feb 26, 2008 at 9:04 AM, Dino Viehland <[EMAIL PROTECTED]> wrote: > What's MakeModule.py? That's from the project I started at http://www.codeplex.com/coils. Suma, you might consider getting a copy of the Codeplex tools and using them to download the most recent changes; I know I've fix

Re: [IronPython] Exporting Python code as an assembly

2008/2/27, Dino Viehland <[EMAIL PROTECTED]>: > What's MakeModule.py? Curt Hagenlocher's work-in-progress tool which was discussed on this list. http://hagenlocher.org/software/ClrWrapper.zip -- Seo Sanghyeon ___ Users mailing list Users@lists.ironpyth

Re: [IronPython] Exporting Python code as an assembly

M To: users@lists.ironpython.com Subject: Re: [IronPython] Exporting Python code as an assembly Hi, I have a py file by name IronPythonDLL.py containing --- import clr import System import sys from ClrWrapper import ClrAttribute, ClrAc

Re: [IronPython] Exporting Python code as an assembly

Hi, I have a py file by name IronPythonDLL.py containing --- import clr import System import sys from ClrWrapper import ClrAttribute, ClrAccepts, ClrReturns class IronPythonClass: clr_namespace = 'IronPythonDLL' @ClrReturns(S

Re: [IronPython] Exporting Python code as an assembly

Hi When i run MakeModule, i am getting this error "AttributeError: 'NoneType' object has no attribute 'GetGetMethod' ". For testing just i was running this command. *.\ipy.exe MakeModule.py Xtest.py -Thanks Raju*** Curt Hagenlocher wrote: > You can download my work-in-progress from > http://

Re: [IronPython] Exporting Python code as an assembly

y, February 06, 2008 3:54 PM To: Discussion of IronPython Subject: Re: [IronPython] Exporting Python code as an assembly The extra __'s are expected. When we enabled this in 1.1.1 we didn't want to significantly alter the experience between 1.1 and 1.1.1. The problem with 1.1 was that i

Re: [IronPython] Exporting Python code as an assembly

hrough my mind :-). Thank you, Rocco -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord Sent: Thursday, February 07, 2008 10:19 AM To: Discussion of IronPython Subject: Re: [IronPython] Exporting Python code as an assembly Pigneri, Rocco wrote: &

Re: [IronPython] Exporting Python code as an assembly

; *From:* [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] *On Behalf Of *Dino Viehland > *Sent:* Wednesday, February 06, 2008 3:54 PM > *To:* Discussion of IronPython > *Subject:* Re: [IronPython] Exporting Python code as an assembly > > The extra __’s are expected. When we enabled

Re: [IronPython] Exporting Python code as an assembly

n of IronPython Subject: Re: [IronPython] Exporting Python code as an assembly The extra __'s are expected. When we enabled this in 1.1.1 we didn't want to significantly alter the experience between 1.1 and 1.1.1. The problem with 1.1 was that if the caller passed in an attribute t

Re: [IronPython] Exporting Python code as an assembly

I've created a project on CodePlex now. It's still in setup mode; send me email and I'll add you to the project there. The only real change I've made since the Feb 5 version are support for static and class methods. And if the class defines a static or class method named "Main", I set that as the

Re: [IronPython] Exporting Python code as an assembly

thonType object into the contructor so the object knows it's type in the Python world. So we probably can't do much about this one :(. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pigneri, Rocco Sent: Wednesday, February 06, 2008 12:47 PM To: Discussion of IronPyth

Re: [IronPython] Exporting Python code as an assembly

55 PM To: Discussion of IronPython Subject: Re: [IronPython] Exporting Python code as an assembly Data binding isn't working for you? We have support for this via CustomTypeDescriptors which describe the Python objects and we have some test cases to verify it works. Note it was broken be

Re: [IronPython] Exporting Python code as an assembly

Well don't I feel like a moron. I should have spotted that. I apologize for posting before thinking. On Feb 5, 2008 4:29 PM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: > On Feb 5, 2008 1:24 PM, Tim Riley <[EMAIL PROTECTED]> wrote: > > I was testing out the code provided and when I tested it usin

Re: [IronPython] Exporting Python code as an assembly

umns = True grid.DataSource = people grid.Dock = SWF.DockStyle.Fill self.grid = grid self.Controls.Add(grid) form = Form() SWF.Application.Run(form) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pigneri, Rocco Sent: Tuesday, February 05, 2008 9:15 AM

Re: [IronPython] Exporting Python code as an assembly

On Feb 5, 2008 1:24 PM, Tim Riley <[EMAIL PROTECTED]> wrote: > I was testing out the code provided and when I tested it using the > example I got the following error. > > [snip] > IOError: Could not add reference to assembly xunit.dll Sorry, you need xunit for that -- it's not part of IronPython.

Re: [IronPython] Exporting Python code as an assembly

I was testing out the code provided and when I tested it using the example I got the following error. Note: I'm using IronPython 2.0 Alpha (2.0.0.800) on .NET 2.0.50727.1433 C:\Documents and Settings\TJRiley\Desktop\ClrWrapper>ipy.exe MakeModule.py Xtest.py Traceback (most recent call last):

Re: [IronPython] Exporting Python code as an assembly

You can download my work-in-progress from http://hagenlocher.org/software/ClrWrapper.zip The source consists of the three files ClrBuilder.py, ClrWrapper.py and MakeModule.py. There are also two "demo" files: Xtest.py and WcfServer.py. The program can currently be run as follows: PS F:\IronPython

Re: [IronPython] Exporting Python code as an assembly

Curt Hagenlocher wrote: > I can't imagine that this would be a problem. It's been a while since > I played with the hosting-level interfaces of 1.1, but I seem to > recall that (at the level in question) they're largely isomorphic with > what's currently in 2.0. Excellent - that's what I thought.

Re: [IronPython] Exporting Python code as an assembly

On Feb 5, 2008 9:15 AM, Pigneri, Rocco <[EMAIL PROTECTED]> wrote: > > To make using these UI controls easier, it would be great if property > statements could be turned into static properties either automatically or > via a flag. Yes, one of the thoughts I had was that you should be able to run su

Re: [IronPython] Exporting Python code as an assembly

On Feb 5, 2008 5:50 AM, Giles Thomas <[EMAIL PROTECTED]> wrote: > > Would it be hugely tricky to get it working in IP 1.1 as well as 2.0, do you > think? > I'm imagining some kind of "--target:1.1" flag to the tool. I can't imagine that this would be a problem. It's been a while since I played w

Re: [IronPython] Exporting Python code as an assembly

herwise, you'll get an exception. Hope that helps, Rocco From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher Sent: Monday, February 04, 2008 1:31 PM To: Discussion of IronPython Subject: [IronPython] Exporting Python code as an as

Re: [IronPython] Exporting Python code as an assembly

Would it be hugely tricky to get it working in IP 1.1 as well as 2.0, do you think? I'm imagining some kind of "--target:1.1" flag to the tool. Michael Foord wrote: Curt Hagenlocher wrote: On Feb 4, 2008 11:07 AM, Michael Foord <[EMAIL PROTECTED]> wrote: Curt Hagenlocher wrote:

Re: [IronPython] Exporting Python code as an assembly

Curt Hagenlocher wrote: > On Feb 4, 2008 11:07 AM, Michael Foord <[EMAIL PROTECTED]> wrote: > >> Curt Hagenlocher wrote: >> >>> The assemblies call into the IronPython engine (version 2) to load and >>> execute the script. Currently, the script is loaded from the file >>> system, but I'd e

Re: [IronPython] Exporting Python code as an assembly

On Feb 4, 2008 11:07 AM, Michael Foord <[EMAIL PROTECTED]> wrote: > >Curt Hagenlocher wrote: >> The assemblies call into the IronPython engine (version 2) to load and >> execute the script. Currently, the script is loaded from the file >> system, but I'd eventually like to support embedding any >>

Re: [IronPython] Exporting Python code as an assembly

Curt Hagenlocher wrote: > The assemblies call into the IronPython engine (version 2) to load and > execute the script. Currently, the script is loaded from the file > system, but I'd eventually like to support embedding any > required scripts as resources in the assembly, so that the whole thin

Re: [IronPython] Exporting Python code as an assembly

The assemblies call into the IronPython engine (version 2) to load and execute the script. Currently, the script is loaded from the file system, but I'd eventually like to support embedding any required scripts as resources in the assembly, so that the whole thing can be distributed as a single ne

Re: [IronPython] Exporting Python code as an assembly

The interface is pretty much exactly what I had in mind for a similar system. What do the statically defined assemblies do - do they call into the IronPython engine - and if so, for IronPython 1 or 2? If not then are you just compiling Python to static assemblies? To my mind the former is more

[IronPython] Exporting Python code as an assembly

After a bit of spare-time hacking this weekend, I've got a "proof-of-concept" program that takes a Python class and exports it as a (statically-defined) assembly. It uses Pythonic function annotations to signal attributes and input and output types to the wrapper generator. You end up with someth