Hello IronPython Community,
It's been a couple of weeks since we released IronPython 1.1.1 RC1 and this
build does not appear to have caused any new issues. As a result I'm pleased
to announce the release of IronPython 1.1.1.
IronPython v1.1.1 is a minor update in which we fixed the most reque
Hello IronPython Community,
I'm pleased to announce the release of IronPython 1.1.1 Release Candidate 1.
For this release we fixed the most requested CodePlex bugs and also a handful
of trivial bugs. In total around twenty bugs have been resolved for 1.1.1 RC1.
Additionally, an issue that wa
: Re: [IronPython] IronPython 1.1.1 wish-list?
That would be great. When may we expect 1.1.1 release?
> Yep, I think this can be fixed. I've got a tentative fix and it looks like
> it works and doesn't break anything. Thanks for bringing attention to this.
>
> -Origin
ilto:[EMAIL PROTECTED] On Behalf Of Kamil
> Dworakowski
> Sent: Friday, January 04, 2008 12:36 PM
> To: [EMAIL PROTECTED]; Discussion of IronPython
> Subject: Re: [IronPython] IronPython 1.1.1 wish-list?
>
> 14632 looks pretty nasty and easy to fix. Good candidate for 1.1.1
4, 2008 12:36 PM
To: [EMAIL PROTECTED]; Discussion of IronPython
Subject: Re: [IronPython] IronPython 1.1.1 wish-list?
14632 looks pretty nasty and easy to fix. Good candidate for 1.1.1?
WeakObject.Equals throws null pointer exception
http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkIt
14632 looks pretty nasty and easy to fix. Good candidate for 1.1.1?
WeakObject.Equals throws null pointer exception
http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=14632
WeakObject is an internal class of IronPython, a component used in WeakHash.
I would especially like it fixed
ionality in the runtime - is there a reason
> you can't use the std lib (other than we don't include it by default? :) ).
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of HEMMI, Shigeru
> Sent: Sunday, December 23, 2
__new__ currently. And if you
> want to always work regardless of version it looks like you can just define
> both __new__ and __init__.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of HEMMI, Shigeru
> Sent: Sunday, December 23
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 1.1.1 wish-list?
Hello,
If the bug,
http://lists.ironpython.com/htdig.cgi/users-ironpython.com/2007-February/004500.html
is fixed or somebody shows me a good example how to inherit "file"
class in IronPython
1.1, I will be happy.
ently. And if you
want to always work regardless of version it looks like you can just define
both __new__ and __init__.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of HEMMI, Shigeru
Sent: Sunday, December 23, 2007 4:00 AM
To: Discussion of IronPython
Su
Also this code path
doesn't exist in v2.0 at all right now so it doesn't suffer from this issue.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vizcayno
Sent: Saturday, December 29, 2007 6:48 AM
To: users@lists.ironpython.com
Subject: Re: [Iro
Hello Dino:
I send you the results running from my DOS WinXP SP2 console:
.ipy -X:ExceptionDetail
IronPython 1.1 (1.1) on .NET 2.0.50727.1433
Copyright (c) Microsoft Corporation. All rights reserved.
['c:\\os\\ipy\\src', 'c:\\os\\ipy\\lib', 'c:\\python25\\lib', 'c:\\os\
\IPY', 'c:\\os\\IPY\\Tutoria
ECTED] [EMAIL PROTECTED] On Behalf Of Vizcayno [EMAIL
PROTECTED]
Sent: Friday, December 28, 2007 9:19 AM
To: users@lists.ironpython.com
Subject: Re: [IronPython] IronPython 1.1.1 wish-list?
Hello:
I have the next problem in Ipy 1.01 I would like to know if it is a
bug to fix in 1.01.1 or not.
Look a
Hello:
I have the next problem in Ipy 1.01 I would like to know if it is a
bug to fix in 1.01.1 or not.
Look at the next code and results running in Ipy 1.01:
IronPython 1.1 (1.1) on .NET 2.0.50727.1433
Copyright (c) Microsoft Corporation. All rights reserved.
['C:\\os\\ipy\\src', 'c:\\python25\\l
Hello,
If the bug,
http://lists.ironpython.com/htdig.cgi/users-ironpython.com/2007-February/004500.html
is fixed or somebody shows me a good example how to inherit "file"
class in IronPython
1.1, I will be happy.
2nd, please provide quit() function, which eases my interactive
IronPython session
Are there any particular bugs you'd like to see fixed in IronPython 1.1.1?
We're planning on updating the 1.1 release w/ a targeted set of bug fixes.
Unfortunately we've started to use the CodePlex bug list to track primarily 2.0
bugs. We can still use this to find the highest ranked bugs that
16 matches
Mail list logo