[IronPython] 2.0B1 Hosting: Creating Python Types
tkapoor at wscm.net
Wed Mar 19 20:34:49 CET 2008
Curt - at pycon, I heard that you are working on a CLR wrapper project.
Under which python code will be have automatically generated wrappers
and that way they can called in C# more easily...
Can you pls provide some details on how the project is going ?
->>Sorry this is not related to the thread.
From: users-bounces at lists.ironpython.com
[mailto:users-bounces at lists.ironpython.com] On Behalf Of Curt
Sent: Wednesday, March 19, 2008 2:15 PM
To: Discussion of IronPython
Subject: Re: [IronPython] 2.0B1 Hosting: Creating Python Types
On Mon, Mar 17, 2008 at 5:26 PM, Dino Viehland
<dinov at exchange.microsoft.com> wrote:
> CodeContext isn't actually internal but it's also not available to you
> hosting APIs.
Does this mean that we shouldn't be creating CodeContexts? I'm using
the class "IronPython.Runtime.Operations.PythonTypeOps+TypeCaller" to
construct new objects from Python types. This process requires a
CodeContext, which I'm currently building from scratch as needed.
(The same approach could be used with the PythonType
"IronPython.Runtime.Builtin.file" in order to build a Python file
object a little more efficiently.)
curt at hagenlocher.org
Users mailing list
Users at lists.ironpython.com
This e-mail and any attachments is confidential and intended solely for the use of the individual(s) to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of Waterstone Capital Management, L.P and affiliates. If you are not the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, printing, forwarding or copying of this email is strictly prohibited. Please contact the sender if you have received this e-mail in error. You should also be aware that e-mails are susceptible to interference and you should not assume that the contents of this e-mail originated from the sender above or that they have been accurately reproduced in their original form. Waterstone Capital Management, L.P. and affiliates accepts no responsibility for information, or errors or omissions in this e-mail or use or misuse thereof. If in doubt, please verify the authenticity with the sender.
More information about the Ironpython-users