Re: [IronPython] __slots__

2009-03-09 Thread Michael Foord
asses. Michael -Original Message- From: users-boun...@lists.ironpython.com [mailto:users- boun...@lists.ironpython.com] On Behalf Of Michael Foord Sent: Monday, March 09, 2009 6:36 AM To: Discussion of IronPython Subject: Re: [IronPython] __slots__ Curt Hagenlocher wrote: On Mo

Re: [IronPython] __slots__

2009-03-09 Thread Dino Viehland
ironpython.com [mailto:users- > boun...@lists.ironpython.com] On Behalf Of Michael Foord > Sent: Monday, March 09, 2009 6:36 AM > To: Discussion of IronPython > Subject: Re: [IronPython] __slots__ > > Curt Hagenlocher wrote: > > On Mon, Mar 9, 2009 at 5:28 AM, Michael Foord > wr

Re: [IronPython] __slots__

2009-03-09 Thread Michael Foord
Curt Hagenlocher wrote: On Mon, Mar 9, 2009 at 5:28 AM, Michael Foord wrote: Curt Hagenlocher wrote: I believe this is already fixed in the current (ie 2.6ish) source. Any chance for 2.0.2? That's Dino's call. The fix in 2.6 is actually a massive restructuring of some c

Re: [IronPython] __slots__

2009-03-09 Thread Curt Hagenlocher
On Mon, Mar 9, 2009 at 5:28 AM, Michael Foord wrote: > > Curt Hagenlocher wrote: >> >> I believe this is already fixed in the current (ie 2.6ish) source. > > Any chance for 2.0.2? That's Dino's call. The fix in 2.6 is actually a massive restructuring of some code, so the backport would likely ha

Re: [IronPython] __slots__

2009-03-09 Thread Michael Foord
Curt Hagenlocher wrote: I believe this is already fixed in the current (ie 2.6ish) source. Any chance for 2.0.2? Michael On Mon, Mar 9, 2009 at 5:19 AM, Michael Foord mailto:fuzzy...@voidspace.org.uk>> wrote: Hello guys, It looks like __slots__ and inheritance are a bit odd in

Re: [IronPython] __slots__

2009-03-09 Thread Curt Hagenlocher
I believe this is already fixed in the current (ie 2.6ish) source. On Mon, Mar 9, 2009 at 5:19 AM, Michael Foord wrote: > Hello guys, > > It looks like __slots__ and inheritance are a bit odd in IronPython > (2.0.1). slots.py: > > class A(object): > __slots__ = [] > class B(A): > __slots__ =

[IronPython] __slots__

2009-03-09 Thread Michael Foord
Hello guys, It looks like __slots__ and inheritance are a bit odd in IronPython (2.0.1). slots.py: class A(object): __slots__ = [] class B(A): __slots__ = [] i = B() i.test = 3 Running with IronPython and CPython: C:\compile\resolver-michael>"C:\Program Files (x86)\IronPython

Re: [IronPython] __slots__ and __str__/__repr__

2006-07-05 Thread Dino Viehland
of IronPython Subject: Re: [IronPython] __slots__ and __str__/__repr__   no, not at all, I just played around at the console trying to find bugs.. :) That said, it probably would suck pretty badly if I was using doctest or something similar.. /S On 7/6/06, Dino Viehland <[EMAIL PROTEC

Re: [IronPython] __slots__ and __str__/__repr__

2006-07-05 Thread Simon Dahlbacka
ce to have an idea how we should prioritize this.    From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Simon Dahlbacka Sent: Wednesday, July 05, 2006 12:29 PM To: Discussion of IronPython Subject: [IronPython] __slots__ and __str__/__repr__   CPython2.4.1 >>>class foo

Re: [IronPython] __slots__ and __str__/__repr__

2006-07-05 Thread Dino Viehland
the obviously most egregious one) and it’d be nice to have an idea how we should prioritize this.    From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Dahlbacka Sent: Wednesday, July 05, 2006 12:29 PM To: Discussion of IronPython Subject: [IronPython] __slots__ and __str__/__re

[IronPython] __slots__ and __str__/__repr__

2006-07-05 Thread Simon Dahlbacka
CPython2.4.1>>>class foo(object):...    __slots__ = ["bar"]...>>>foo.bar>>> f = foo()>>> f.barTraceback (most recent call last):   File "", line 1, in ?AttributeError: barIronpython beta8>>>class foo(object):...    __slots__ = ["bar"]>>>foo.bar >>> f = foo()>>> f.barTraceback (most recent call last