Wiley Professional Python Frameworks: Web 2.0 Programming with Django and Turbogears 978-0-470-13809-0 Manuale Utente
Codici prodotto
978-0-470-13809-0
Web 2.0, Python, and
Framewor ks
You had me at “Hello.”
— Renée Zellweger in Jerry Maguire
The authors know you. Or at least they know a few things about you. If you’ve grabbed this book
from your favorite online (or even brick-and-mortar) bookseller, chances are that you’re an accom-
plished Python developer, or you’re on your way to becoming one. You may well have created
web content using your Python skills, or perhaps you’ve written your share of web services
backed by Python code as a Common Gateway Interface (CGI) script. You may have just heard the
term “Web 2.0” or “AJAX,” or you may already be an accomplished user of one or many Web 2.0
sites and are wondering how to plug into the action as a developer. You may be aware of web
frameworks in other languages, such as Ruby on Rails (also referred to simply as Rails) or Google
Widget Toolkit (GWT), and you may even have experimented with one or more them. If you’ve
been unable to embrace any of these other frameworks, it may be because they have one annoying
aspect — they’re not Python. Actually, if you’ve worked with other frameworks, the fact that they
don’t follow the Python philosophy (they’re not Pythonic ) may be the least of your negative
impressions.
from your favorite online (or even brick-and-mortar) bookseller, chances are that you’re an accom-
plished Python developer, or you’re on your way to becoming one. You may well have created
web content using your Python skills, or perhaps you’ve written your share of web services
backed by Python code as a Common Gateway Interface (CGI) script. You may have just heard the
term “Web 2.0” or “AJAX,” or you may already be an accomplished user of one or many Web 2.0
sites and are wondering how to plug into the action as a developer. You may be aware of web
frameworks in other languages, such as Ruby on Rails (also referred to simply as Rails) or Google
Widget Toolkit (GWT), and you may even have experimented with one or more them. If you’ve
been unable to embrace any of these other frameworks, it may be because they have one annoying
aspect — they’re not Python. Actually, if you’ve worked with other frameworks, the fact that they
don’t follow the Python philosophy (they’re not Pythonic ) may be the least of your negative
impressions.
The good news is that now you don’t have to abandon the language that you love to get the
(admittedly significant) benefits of a comprehensive framework. The Python-based frameworks
covered in the chapters that follow are every bit as capable and fun to use as any other, and it
might be argued, perhaps even better in some ways. The Rails language, for example, demands a
certain adherence to convention that sometimes gets in the way of a coder’s freedom of expression.
GWT is essentially a Java-based page-element composer that enables you to bypass writing
ECMAScript directly, but lacks the design center for dynamic partial page replacement for which
the Python Turbogears framework is becoming renowned.
(admittedly significant) benefits of a comprehensive framework. The Python-based frameworks
covered in the chapters that follow are every bit as capable and fun to use as any other, and it
might be argued, perhaps even better in some ways. The Rails language, for example, demands a
certain adherence to convention that sometimes gets in the way of a coder’s freedom of expression.
GWT is essentially a Java-based page-element composer that enables you to bypass writing
ECMAScript directly, but lacks the design center for dynamic partial page replacement for which
the Python Turbogears framework is becoming renowned.