Hello IronPython community,
Today we have released IronPython 0.7.5. The bugs we fixed for this
release are:
* Can't Open 2 or more IronPythonConsoles
* File share error when opening the file for reading multiple times
* Generate assembly in the same directory as the Python source
* Can't OR flag
Hello,
After reading Anthony's email on CPython's standard libraries I tried to
import the libraries using IronPython to see how well IronPython does
just importing the libraries. Out of 182 modules that I tried to import
116 imported successfully (which does not unfortunately mean that they
would
Martin,
Great post!
Keep up the good work and don't forget to also have some _fun_ in
Hawaii and Prague (great beer and since I live in Munich you can take
my word for it ;-)
Safe trip!
Anthony
On 5/17/05, Martin Maly <[EMAIL PROTECTED]> wrote:
Hello,After reading Anthony's email on CPython's
Martin,
I think that while fixing the 'assemblies in the same directory' bug, a new critter may have been introduced...
StringIO used to work in IP-0.7.4, now using IP.0.7.5 I see the following trackback..
IronPython 0.7.5 on .NET 2.0.40607.42
Copyright (c) Microsoft Corporation. All rights res
Strange that someone reported similar thing on GotDotNet
forums. I believe that the cause is an old version of .Net.
You need .Net 2.0 Beta 2 to run
IronPython:
IronPython 0.7.5 on .NET 2.0.50215.44Copyright (c) Microsoft
Corporation. All rights reserved.>>> import
StringIO>>>
You can get
With some code changes in IronPython (the changes are
not in 0.7.5) I was able to get this working as far as making word app visible.
However I was not yet successful with the Documents collection
access.
The object returned from the Documents property (and this
was just a quick look, I am g
On 5/17/05, Martin Maly <[EMAIL PROTECTED]> wrote:
> Hello,
>
> After reading Anthony's email on CPython's standard libraries I tried to
> import the libraries using IronPython to see how well IronPython does
> just importing the libraries. Out of 182 modules that I tried to import
> 116 imported
As I said, what I did was merely import the files. I did not run them.
That will be the next step.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of John Doty
> Sent: Tuesday, May 17, 2005 4:36 PM
> To: Discussion of IronPython
> Subject: Re: [Iro
Is this bug known?
In file foo.py:
import bar
At the IronPython console:
>>> import foo
[[ Giant exception stack trace ]]
>>> import foo
>>>
That is, if a module fails to import, a second attempt to import does
not throw an exception. I think this is because
Importer.LoadFr
> Is this bug known?
> That is, if a module fails to import, a second attempt to import does
> not throw an exception. I think this is because
> Importer.LoadFromSource puts the module into sys.modules before
> calling the import function, but does not remove it if the import
> function fails.
I b
On May 17, 2005, at 10:42 PM, Curt Hagenlocher wrote:
Is this bug known?
That is, if a module fails to import, a second attempt to import does
not throw an exception. I think this is because
Importer.LoadFromSource puts the module into sys.modules before
calling the import function, but does not re
On 5/17/05, Curt Hagenlocher <[EMAIL PROTECTED]> wrote:
> > Is this bug known?
> > That is, if a module fails to import, a second attempt to import does
> > not throw an exception. I think this is because
> > Importer.LoadFromSource puts the module into sys.modules before
> > calling the import fun
> On May 17, 2005, at 10:42 PM, Curt Hagenlocher wrote:
>
> > I believe that this behavior is consistent with that of CPython.
>
> Consistent with CPython < 2.4. The behavior has changed.
Figures. I'm still using 1.5.2 :)
--
Curt Hagenlocher
[EMAIL PROTECTED]
_
On May 18, 2005, at 12:23 AM, Curt Hagenlocher wrote:
On May 17, 2005, at 10:42 PM, Curt Hagenlocher wrote:
I believe that this behavior is consistent with that of CPython.
Consistent with CPython < 2.4. The behavior has changed.
Figures. I'm still using 1.5.2 :)
And you have a version of Window
Bob Ippolito writes:
> On May 18, 2005, at 12:23 AM, Curt Hagenlocher wrote:
>> Figures. I'm still using 1.5.2 :)
>
> And you have a version of Windows new enough to run .NET 2.0?
> Amazing :)
Hey, 1.5.2 works just fine on Windows 2003!
--
Curt Hagenlocher
[EMAIL PROTECTED]
___
15 matches
Mail list logo
