Pyc.py is now in TFS on CodePlex,
$/IronPython/IronPython_Main/Tools/Scripts/pyc.py, and a few related tests have
been added to our checkin system ensuring this doesn't get broken in the future.
Dave
-Original Message-
From: users-boun...@lists.ironpython.com
I have embedded IronPython 2.01 into my C# application, and am
extremely impressed by the ease of integration and the
interoperability with the .NET types. However I am a bit stumped by
something that probably is quite simple.
1) In a python script, I import one of my application types.
2) From
There is an implicit conversion from PythonType - Type. So
(Type)(PythonType)o will work here. Alternately you can just strongly type a
function in C# as taking a Type and call that from Python and the conversion
will happen automatically.
-Original Message-
From:
Excellent! Thanks.
On Thu, Apr 9, 2009 at 12:19 PM, Dino Viehland di...@microsoft.com wrote:
There is an implicit conversion from PythonType - Type. So
(Type)(PythonType)o will work here. Alternately you can just strongly type a
function in C# as taking a Type and call that from Python and
For the archives, this is raised as:
http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=21987
On Thu, Apr 9, 2009 at 4:42 PM, Dave Fugate dfug...@microsoft.com wrote:
Pyc.py is now in TFS on CodePlex,
$/IronPython/IronPython_Main/Tools/Scripts/pyc.py, and a few related tests
have
Has it ever worked for you or have you always gotten this error?
On Wed, Apr 8, 2009 at 11:34 AM, Daryl Hendricks dhendri...@msn.com wrote:
Hello,
I'm running into a problem where I can't use the XAML editor in the
isolated version of IronPython Studio. The error I'm getting is Package
IronPython 2 targets CPython 2.5 compatibility. In 2.5, you need the
__future__ line in order to use the with statement. It's quite possible
that this wasn't implemented yet in that alpha or beta of IronPython.
It's in 2.6 where you don't need the from __future__ import
with_statement.
On Fri,
