GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [Python-Dev] Problems with the new super()
  • [Python-Dev] Problems with the new super()
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Problems with the new super()

[Python-Dev] Problems with the new super()

Phillip J. Eby pje at telecommunity.com
Thu May 1 22:00:02 CEST 2008

  • Previous message: [Python-Dev] Problems with the new super()
  • Next message: [Python-Dev] Problems with the new super()
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

At 04:38 PM 5/1/2008 -0300, Facundo Batista wrote:
>Has super() proved more useful than harmful?

For me, yes.  I use it all the time.  The only time I use 
explicit-target upcalls is in __init__ methods, and there usually 
only to skip a subclass' init or to explicitly manage a tricky bit of 
multiple inheritance.

(Note, by the way, that you cannot safely write an upcall in a mixin 
class without super, so it can't safely be done away with, anyway.)


  • Previous message: [Python-Dev] Problems with the new super()
  • Next message: [Python-Dev] Problems with the new super()
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.