Setter Propertys' mro?

gt;>> t.p=5 >>> t.p 4 why do i have to set the __metaclass__ ? this seems like a bug? i know that i probably shouldn't worry about this because if a programmer does want to set my value and it causes an error, thats his problem but this bothers me. whats the point of the __set__ method then? Thanks in advanced. -- Cipher -- http://mail.python.org/mailman/listinfo/python-list

Re: found a bug with smtpd, where can i report this?

On Sep 5, 4:01 am, "Marcus.CM" <[EMAIL PROTECTED]> wrote: > Hi, > > Where should i report the bug? > smtpd bug. > > Marcus.CM http://bugs.python.org/ -- http://mail.python.org/mailman/listinfo/python-list

Re: Setter Propertys' mro?

On Sep 6, 9:10 pm, Steven D'Aprano <[EMAIL PROTECTED] cybersource.com.au> wrote: > On Sat, 06 Sep 2008 18:15:33 -0700, cipher wrote: > > Whats the mro (method resolution order) of a setter property (__set__ on > > a descriptor). > > i seem to be experiencing some we