should I put old or new style classes in my book?

Benjamin Kaplan benjamin.kaplan at case.edu
Thu May 29 13:56:22 EDT 2008


On Thu, May 29, 2008 at 12:07 PM, <allendowney at gmail.com> wrote:

> Hi All,
>
> I am working on a revised edition of How To Think Like a Computer
> Scientist,
> which is going to be called Think Python.  It will be published by
> Cambridge
> University Press, but there will still be a free version under the GNU
> FDL.
>
> You can see the latest version at thinkpython.com; I am revising now,
> so
> I welcome all comments, suggestions, corrections, etc.
>
> Anyway, I am posting to ask about the current status of new style
> classes.
> I am planning to present only one style in the book, because the
> differences
> between them don't matter for anything I am doing in the book.
>
> The current edition of the book presents old style classes.  I am
> considering
> switching to new style classes on the assumption that this should be
> the default
> choice for new programs.  The drawback is that a lot of the online
> documentation
> still uses old style classes.
>
> Thanks for any guidance you can provide.
>
> Cheers,
> Allen
>  <http://mail.python.org/mailman/listinfo/python-list>


Definitely go with the new-style classes. Python 3 is coming out soon, which
doesn't have classic classes.

http://docs.python.org/dev/3.0/whatsnew/3.0.html#new-class-and-metaclass-stuff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20080529/dca4c0cb/attachment-0001.html>


More information about the Python-list mailing list