Coils: a static class wrapper for IronPython

CREATED ISSUE: Create PowerShell extension in Python

CurtHagenlocher — Wed, 09 Apr 2008 20:54:05 GMT

This would be a good demo of the technology.

NEW POST: Design Thoughts

CurtHagenlocher — Mon, 24 Mar 2008 16:16:57 GMT

A single application of Coils to a Python project should result in a single assembly being created. This assembly should be associated with its own ScriptRuntime object so that it's isolated from any other script-based code in the same process.

The assembly will create a single "manager" class with references to the ScriptRuntime and ScriptEngine. It will also create one "wrapper" class for each Python type being wrapped.

The wrapper class will have a shared reference to the PythonType and a per-instance reference to the actual object being wrapped.

CREATED ISSUE: Create explicit wrapper constructor

CurtHagenlocher — Wed, 13 Feb 2008 23:02:54 GMT

It should be possible to wrap an existing IronPython (dynamic) object with the static class. This could be done as a static function
T FromObject(object obj, bool suppressCheck)
which tests to make sure that the object is of the appropriate type (unless suppressCheck = true)

CREATED ISSUE: Recognize Pythonic default parameters

CurtHagenlocher — Wed, 13 Feb 2008 22:51:14 GMT

A Python method declaration like this:
def DoThis(self, a, b=1, c=2):

should be translated into three methods on the wrapper:
void DoThis(a)
void DoThis(a, b)
void DoThis(a, b, c)

CREATED ISSUE: Allow constructor to have parameters

CurtHagenlocher — Wed, 13 Feb 2008 22:46:43 GMT

The current wrapper assumes that the Python __init__ function is parameterless. It should not.

Source code checked in

CurtHagenlocher — Sun, 10 Feb 2008 00:01:05 GMT

Fixed constructor to call __init__

CLOSED FEATURE: Expose Python properties on generated class

CurtHagenlocher — Sat, 09 Feb 2008 00:30:42 GMT

Wrap Python properties (at least the "get" and "set" functions) as properties on the generated class
Comments: Implemented.

COMMENTED FEATURE: Expose Python properties on generated class

CurtHagenlocher — Sat, 09 Feb 2008 00:30:10 GMT

Wrap Python properties (at least the "get" and "set" functions) as properties on the generated class
Comments: ** Comment from web user: CurtHagenlocher **

Use "ClrProperty" instead of "property" to specify the type of the property.

Source code checked in

CurtHagenlocher — Sat, 09 Feb 2008 00:29:03 GMT

Added support for properties

UPDATED WIKI: Home

CurtHagenlocher — Thu, 07 Feb 2008 15:56:52 GMT

Project Description
The goal of the Coils project is to generate static CLR class wrappers for classes implemented in (Iron)Python. In addition to simplifiying use of Python code from non-DLR environments, this will allow access to .NET features which require class- and method-level attributes (such as serialization and WCF).

This project is still in the very preliminary stages.

UPDATED WIKI: Home

CurtHagenlocher — Thu, 07 Feb 2008 15:55:17 GMT

Project Description

The goal of the Coils project is to generate static CLR class wrappers for classes implemented in (Iron)Python. In addition to simplifiying use of Python code from non-DLR environments, this will allow access to .NET features which require class- and method-level attributes (such as serialization and WCF).

This project is still in the very preliminary stages.

CREATED ISSUE: Expose interfaces on generated code

CurtHagenlocher — Thu, 07 Feb 2008 15:53:59 GMT

Identify CLR interfaces that are bases of the class being wrapped but are not part of the IronPython implementation. Expose those interfaces on the wrapper and generate appropriate methods that forward to the Python implementation.

CREATED ISSUE: Scan multiple .py files

CurtHagenlocher — Thu, 07 Feb 2008 15:48:56 GMT

Allow scanning of multiple .py files in a single pass by specifying multiple file names using wild cards on the command line.

CREATED ISSUE: Embed .py files as resources

CurtHagenlocher — Thu, 07 Feb 2008 15:46:58 GMT

Allow .py files to be embedded in the assembly as resources. Modify code generation to allow loading of modules from resources. This would allow an IronPython library or application to be delivered with no external .py files. Once this is working, Coils can be distributed as an actual .EXE.

CREATED ISSUE: Support IronPython 1.1

CurtHagenlocher — Thu, 07 Feb 2008 15:43:00 GMT

Have two code generators and pick between them using a command-line switch.

CREATED FEATURE: Allow EXE generation

CurtHagenlocher — Thu, 07 Feb 2008 15:42:12 GMT

Use a command-line switch to choose between /target:exe, /target:winexe or /target:library. For exe and winexe, exactly one class being wrapped must define a classmethod or staticmethod named "Main" with an appropriate signature.

CREATED TASK: Separate inspection from code generation

CurtHagenlocher — Thu, 07 Feb 2008 15:40:21 GMT

Currently, the code performs inspection and code generation as basically a single step. Change this so that inspection happens first and generates a description of the classes to be created. Pass this description to the code generator.

CREATED FEATURE: Expose Python properties on generated class

CurtHagenlocher — Thu, 07 Feb 2008 15:38:05 GMT

Wrap Python properties (at least the "get" and "set" functions) as properties on the generated class

UPDATED WIKI: Home

CurtHagenlocher — Thu, 07 Feb 2008 13:53:40 GMT

Project Description

The goal of the Coils project is to generate static CLR class wrappers for classes defined in IronPython. In addition to simplifiying use of Python code from non-DLR environments, this will allow access to .NET features such as serialization and WCF that require class- and method-level attributes.

Source code checked in

CurtHagenlocher — Thu, 07 Feb 2008 13:50:39 GMT

Initial version; really just a "proof-of-concept"