On 12/28/05, Karl Guertin <[EMAIL PROTECTED]> wrote: > There have been significant changes in the framework but the only one > that should affect 0.8 users is the splitting of @expose into @expose > and @validate (at least I think it's validate, it happened yesterday) > and I think that was made to be backwards compatible. Upgrading will > get you newer versions of the components (Cherrypy, Kid) and I don't > think there are any incompatible changes there.
FYI: I try to keep the CHANGELOG.txt file up-to-date with a list of changes as intended for human consumption (unlike an svn log, for example). Here are 0.9's backwards incompatible changes: * turbogears.expose no longer provides JSON by default. You need to turn on JSON via the config file or by the allow_json parameter to expose. * The server.webpath configuration variable will not only properly set outgoing URLs, but will also "fix" incoming URLs if TurboGears is running as some path underneath another webserver. If you were previously running a CherryPy filter to handle this, you no longer need to. I'm hoping that we can declare the 0.9 API stable soon (with the possible exception of widgets, which may not be declared "stable" until 1.0, because I really want to give people time to comment on that). In some ways, I regret that the 0.8 series is called "alpha", because while it is alpha, it's hard to figure out what to call the first 0.9 release. (alphalpha? prealpha? gadzooks). Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
