[IronPython] IronPython 1.1.1 wish-list?
dinov at exchange.microsoft.com
Wed Jan 2 20:56:54 CET 2008
FYI this one is already fixed in the v2.0 tree, but I'll look at fixing it in v1.1.1 as well - it's a little more invasive than I'd usually want but it shouldn't be too bad.
But if you want to work around it for the time being you can replace __init__ w/ __new__:
def __new__(cls, fname):
x = TESTINGwrite("testing_TMP.txt")
We just have the functionality of __init__ in __new__ currently. And if you want to always work regardless of version it looks like you can just define both __new__ and __init__.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of HEMMI, Shigeru
Sent: Sunday, December 23, 2007 4:00 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 1.1.1 wish-list?
If the bug,
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
2007/12/18, Dino Viehland <dinov at exchange.microsoft.com>:
> 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 aren't
> fixed in v1.1 and target those to be back ported - but it's possible we
> might miss something important. So I'd thought I'd ask: what do you want
> Note the idea here is to keep these fixes small and keep the release stable,
> so please no fix "type(type) is type" J. And of course if you don't know
> how bad it'll be feel free to suggest it anyway. Thanks!
> Users mailing list
> Users at lists.ironpython.com
Users mailing list
Users at lists.ironpython.com
More information about the Ironpython-users