Hi Max,
If you downloaded it from the 2.6.1 release page, then IronPython.msi should be
the correct version. The other MSI you mention is for the release candidate
(RC), not the final release. Go ahead and run IronPython.msi, and just to be
safe, you can fire up the IronPython Console and make
('Microsoft.Scripting')
clr.AddReference('Microsoft.Scripting.Core')
clr.AddReference('Microsoft.Scripting.Debugging')
clr.AddReference('Microsoft.Scripting.ExtensionAttribute')
clr.AddReference('mscorlib')
clr.AddReference('System')
clr.AddReference('System.Data')
On Thu, Apr 29, 2010 at 5:13 PM, David DiCato
This is probably an assembly load failure. Try copying c:\Program
Files\IronPython 2.6\*.dll into your program directory. You will also need to
make sure that sys.path is properly set if you're using the CPython standard
lib for anything.
We realize this is kind of an undesirable workaround,
Hello Python Community,
We're pleased to announce the final release of IronPython 2.6.1. This version
of IronPython makes great strides in stability and compatibility, including a
considerable number of targeted bugfixes. This is our largest servicing release
to date, and with your help both
The fix for this is now checked in and has been pushed to CodePlex. Thanks for
reporting!
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of David DiCato
Sent: Friday, February 19, 2010 12:31 PM
To: Discussion of IronPython
Subject: Re: [IronPython
Hi Justin, this is definitely a valid bug; thanks for reporting it. We’re
supposed to ignore any methods named GetMember/SetMember/DeleteMember unless
they define the [SpecialName] attribute, but we fail to account for cases where
there could be overloads. This is because the default binder
In IronPython, clr is a builtin module, so this error should theoretically be
impossible. How did you run the script when it gave you the Can not import
module clr error?
-Original Message-
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf
Hello Python Community,
We're pleased to announce the release of IronPython 2.6.1 RC1. This version of
IronPython makes great strides in stability and compatibility, including a
considerable number of targeted bugfixes. Because this is our largest servicing
release to date, and due to our
: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of David DiCato
Sent: Tuesday, January 26, 2010 4:58 PM
To: Discussion of IronPython
Subject: Re: [IronPython] to invoke ironpython from runtime in .NET framework
4.0
The DLR is not exclusively for .NET 4.0
The DLR is not exclusively for .NET 4.0, and until recently, it was not part of
the framework. Starting with .NET 4.0, core bits of the DLR have been added as
a feature.
IronPython 2.6 runs on .NET 2.0 SP1 and contains its own distribution of the
DLR. The release page refers to this
You need to instantiate InstalledFontCollection in order to use its Families
field directly. The code sample you sent gets Families from the type
InstalledFontCollection, rather than an instance thereof, and thus tries to
iterate over a property descriptor. Try the following:
for f in
Hello Python Community,
I am delighted to announce the release of IronPython 2.0.3. This release is a
minor update to IronPython 2.0.2 and the latest in a series of CPython
2.5-compatible releases running on the .NET platform. Again, our priority was
to make IronPython 2.0.3 a bugfix release
Very cool - it's always fulfilling for us to see this level of enthusiasm from
our users. Unfortunately, the legal barriers to our accepting external
contributions are still very much there, as explained in the FAQ
(http://ironpython.codeplex.com/Wiki/View.aspx?title=FAQ). As for the CodePlex
As we work towards our IronPython 2.0.3 bugfix release, Dino and I would like
to get a feel for which bugs left unresolved in 2.0.2 are most important for us
to fix in the next release. Please let us know ASAP if there's an issue you'd
like to see fixed in IronPython 2.0.3. Thanks!
You have to pass the required options to Python.CreateEngine, like so:
var options = new Dictionarystring, object();
options[EnableProfiler] = ScriptingRuntimeHelpers.True;
ver engine = Python.CreateEngine(options);
Hope this helps,
- David
From: users-boun...@lists.ironpython.com
Hello Python Community,
I am delighted to announce the release of IronPython 2.0.2. This release is a
minor update to IronPython 2.0.1, which in turn is a CPython 2.5-compatible
release running on the .NET platform. Our priority was to make IronPython 2.0.2
a bugfix release that remains
Seo is correct; in order to import random, you need the CPython standard
library in sys.path. There are 3 ways to do this:
1. Run IronPython from the standard library directory (the working
directory is in sys.path by default)
2. Append the standard lib directory to sys.path for
This is more a question about the Office/Word APIs than anything
IronPython-specific, so I'd point you to
http://msdn.microsoft.com/en-us/library/bb243297.aspx as a starting point.
As far as I know, you can't embed arbitrary files in a Word document, so I'd
recommend converting your HTML to a
Hmm, the fact that we aren't picking up __radd__ properly looks like a bug,
which I'll go ahead and log on CodePlex. The good news is that there's a more
common usage pattern that works correctly.
The canonical way to do this is to define + and - as static (Shared in VB
speak) operator
Hi Patrick,
I'm in the process of looking into this for you. As you mentioned, the
traceback module (e.g. traceback.print_exc()) is the way to go, and it should
work in 2.6. Which version of IronPython are you using?
As a temporary workaround, you can use the sys module to get most of the same
20 matches
Mail list logo
