In the past few weeks a number of issues have been addressed with
TG2.1 and it’s time to push out a new release with those fixes.  Here
is an overview.

Front-ported Beaker Secret key functionality.
Fixed i18n hitting the filesystem on every call.
Fixed #2287, allowing genshi to now output xhtml.
Fixed #2273, allowing TW config from within the paste.ini file.
Fixed #2237, allowing initializing config before app setup to give
setup access to configuration settings.
Fixed #2357, script_path was not properly carried through to dispatch.
Fixed #2167, tgext.admin was not allowing for integrity errors to pass
thru from post/put.
Fixed #2373, Returning a list for an exposed json template now raises
a meaningful exception.
Fixed #2247, strict_c is now the default for the TurboGears
configuration in debug mode.

Benchmarking 2.1a2, it’s about 20% faster than 2.1a1 because it no
longer accesses the filesystem on every request.  We have also fixed
the problem with repoze.what where it would access the database the
same number of times as you have groups registered to the user, which
can have a large impact

It seems that 2.1a1 has the same beaker secret key flaw that 2.0.1
had, and we have addressed this in 2.1a2.  So, if you are running a
2.1a1 site, it is highly recommended that you provide:

beaker.session.secret = somesecret

in your .ini file where somesecret has some sort of different value.

Some more work has gone into the docs, specifically an expansion to
the docs on what is generated when you quickstart a new project has
been added: http://www.turbogears.org/2.1/docs/main/QuickStart.html

If you have a 2.1a1 site, simply: easy_install -U TurboGears to
upgrade.

There will likely be 1 more alpha before we lock down the api, heading
into a beta state.

cheers.
-chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to