great hope for this project in these new hands and look
forward to watching their future successes.
So long and thanks for all the fish - Jim Hugunin
(original of this message is posted at
http://hugunin.net/microsoft_farewell.html)
___
Users mai
Another option would be to use the System.Windows.Automation library - new in
.NET 3.0. It's a lot easier to use than the native APIs when it works for you.
This sample will print the titles of all the top-level windows.
--
import clr
clr.AddReference('UIAut
I believe that I fixed both the private archive and the header issues. I'm
still looking into what happened with my hosting service (dreamhost) last night
to cause this and avoid it in the future. A mailman upgrade does sound like
the most likely cause.
Thanks - Jim
-Original Message
John Lam announced this morning that we will be accepting external source code
contributions into the IronRuby libraries on the standard Ruby open source
site, Rubyforge. In the hours since that announcement a number of people
(including Mark, below) have asked if we're going to do the same thi
My answers are inline for your first four questions. I don't have time to fill
out the rest right now, but I thought that you'd rather have a partial answer
than to wait on something more thorough that may or may not come.
Thanks - Jim
1) Can a developer extend the language by adding new key
Keep in mind that the DLR is shipped with full sources that same way that
IronPython itself is on codeplex. It should be able to run the full stack on
any fully compliant CLI implementation.
In addition to that, with the Silverlight announcements we made today,
IronPython is already running on
I'd like to point out one fact about these benchmarks that seems to have been
missed. Seo's numbers are for running IronPython 1.1 on Mono - not on the
Microsoft .NET implementation. The Mono team has done excellent work with that
project, but today the performance of the .NET implementation i
re also looking at
the bigger picture to make all dynamic languages deeply integrated with the
.NET platform and with technologies and products built on top of it. I'm
excited about how far we've come, but even more excited by what the future
holds!
Thanks - Jim Hugunin (for the Iron
g else. I'm quite excited that we've
been able to keep the good performance aspects of that initial prototype in the
1.0 release. Here's a copy of data from the original email that I sent about
IronPython 0.1:
------------
Da
Two things that I use to help with this
are site.py and execfile.
Site.py is a Python file that will be
automatically executed when you start IronPython. It’s a standard Python
feature. I use this to add the standard Python 2.4 directory to my path as
well as to add refererences (usin
Dino's right that this is behavior that we'd like to make more natural and that
we'll look into fixing.
However, there's a classic python-style work-around for this issue that can
also be used to handle the case where a class implements two conflicting
interfaces. This relies on the fact that
The current beta 1 release of IronPython always pops up a console. One of our
pre-1.0 workitems is to add a way to launch IronPython applications without
popping up a console, but we don't have that yet. The idea is that anyone
who's willing to work with a 1st beta should be willing to deal wi
Hi Jeff,
It would be cool to see IronPython running in Komodo.
The makefile doesn't work out of the box on anything except MS's SSCLI
implementation. Your change to gmcs looks like the right one to compile on
Mono. The TAB bug is one we need to fix.
The general experience people report with
If you'd like to work with us on IronPython and the underlying runtime support
for dynamic languages that makes it possible, we have a few positions
available. We're looking for one developer, one program manager, one tester
and at least one summer intern. See my blog for links to a little mor
There are a number of serious bugs that people have encountered using the
interactive console in IronPython 1.0beta1. These bugs are caused by major
changes that we (actually I) made to the way the interactive console works for
this release. These changes removed a long-standing memory leak th
MSI packaging has been very low on our
list since my impression is that most IronPython users are happier with the zip
file style of installation where you can know exactly where everything came
from and went. If there’s interest in an MSI installer we can prioritize
it higher. We expect
We've just released the first beta of IronPython 1.0 and are entering the home
stretch to a 1.0 final build. This build includes many bug fixes for issues
reported to us by the community as well as many changes to get better
compatibility with CPython 2.4. With this build we've addressed the m
Because IronPython wasn't written targeting CF from the start, I suspect that
there are lots of little cases where we used APIs that aren't supported.
However, because IronPython tries to only use core APIs I suspect that this
would be a modest amount of work.
The one exception to that is that
The workaround that I use is execfile, i.e.
> IronPythonConsole
>>> execfile('foo.py')
This is exactly what python -i foo.py does for you.
-Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Jacobs
Sent: Tuesday, December 06, 2005 12:41 AM
To:
I’ve started blogging again now that we’ve
shipped .NET 2.0. My most recent blog is about an IronPython demo video that
you can download from the MSDN site. Links are available here:
http://blogs.msdn.com/hugunin/default.aspx
I hope to follow-up soon with technical blogs on the har
Hi Keith,
I think that we overstated the
announcement of static compilation a little bit. There is a new class that
does support some static compilation, but it’s far from complete. We
only expose the class and no msbuild or command-line way of invoking the
compiler so you’ll need to
Thanks for the bug report. We’ll
add it to the list to fix. I assume that you know that you can do this as
a work-around:
property(_getValue,
None, None, “This is doc”)
The unhandled exception change is my
fault. I made the change because it makes debugging IronPython
applications
I can make some fairly small changes to this test and find that
IronPython is about 1.3x faster than CPython on roughly the same code.
The fact that I need to make changes is obviously not a good thing.
However, the changes that I made help show the kinds of rough edges we
have left before getting
23 matches
Mail list logo
