Though many people say good words for pylons, I believe TurboGears is
still a good choice for me at this time:

• TG is one year older than Pylons, which means more stable most of
  the time
• TG comes with more tools that is handy. Say for
  internationalization, TG is much easier. It can handle strings in
  both the Python files and template. It also do the language choose
  automatically.
• The major difference between the two is the dispatching
  mechanisms. Though Pylons’ URL matching is more flexable, I found
  the TurboGears tree like structure quite nature, as some one from
  Quixote.
• TurboGears comes with AJAX support
• TurboGears comes with a good widget library, and many more in the
  cogbin. ToscoWidgets, which is seperated from TurboGears, will be
  used in the future release of both. And for sure it will be much
  easier to switch to ToscoWidgets from TG than from Pylons.
• One thing TG lakes is the caching. However when it comes in a
  future release, I can benefit from it with little or no change of
  my application code.
• TG returns a dict/JSON from the controller. This seperates the view
  and controller, and makes multiple views (say HTML and RSS feed)
  quite easier. While the “c” global accross controller and templage
  is, well, rather urgly from my point of view.

Share This

This works fine most of the time. However, the Python function name is
quite restrict than what we can use in an URL. For example, the “.”
character is not allowed. So, for example, if I want to make the URL
looks the old traditional way, like “/index.html”. I’ll need to write
a BIG elif clause in the default() function.

The good news is that after some digg on Google I found
This CherryPY ticket. And the solution is simple: I could use
index_html as the function name, and when user types index.html in the
URL, CherryPY will find index_html

Share This