TurboGears 1.0.7 released
Florent Aide
I am pleased to announce the release of TurboGears 1.0.7, a new stable
release that fixes even more bugs. If you tried 1.0.6 it is
recommended you upgrade to 1.0.7 because is fixes an issue which was
introduced in 1.0.6 and resulted in errors when using the identity
framework to redirect on error pages.
1.0.x users are encouraged to upgrade their applications to this release.
I'd like to thank one more time the people who are working tirelessly
behind the scene to provide you with quality releases and lively
support on the mailing lists. Thank you all guys, you're the
community. I'd also like to thank all our users out there who are
sometimes just using TG without posting in our mailing lists, but who
are posting some small "I use TG" on their blogs... Please continue to
do so! :)
Florent Aide.
Daniel Fetchinson
I just did an easy_install -U TurboGears (I already had 1.0.3.2 and
1.0.4.4) and this grabbed 1.1b1 which is not what I wanted. I had no
intention of installing a beta, I was going for 1.0.7. Is it
easy_installable?
Another question: there are two intertwined tickets, 1709, 1710, which
includes my patch to scheduler.py which makes it possible to execute
one task once, something that is useful for a long running task. Some
time ago I was asking about this and you guys said it will be included
but 1.1b1 still does not have it applied. Any chance this will happen?
(The name 'onetime' in 1709 changed to 'single' in 1710 (or the other
way around) contributing to the confusion already present by the two
tickets on the same issue. This happened because I created one ticket
and a reader of the dev list created another. If it will make things
clearer I can create a final ticket and the two previous can be
labeled duplicate or closed or something.)
Cheers,
Daniel
> >
>
--
Psss, psss, put it down! - http://www.cafepress.com/putitdown
iain duncan
Thanks Florent!
If this one is a stable bug fix, maybe we should hassle Webfaction to
get it added to their control panel? I just set up an app there today
and had to do all kinds of wacky upgrade stuff as the latest install
from them is 1.0.4 with no SA or Genshi.
I'm happy to do some hassling if you think this is a good release to
hassle for.
Iain
Christopher Arndt
> I just did an easy_install -U TurboGears (I already had 1.0.3.2 and
> 1.0.4.4) and this grabbed 1.1b1 which is not what I wanted. I had no
> intention of installing a beta, I was going for 1.0.7. Is it
> easy_installable?
Yes, with "easy_install TurboGears==1.0.7". But the recommended and
supported way ist to use tgsetup.py, as explained on
http://docs.turbogears.org/Install.
> Another question: there are two intertwined tickets, 1709, 1710, which
> includes my patch to scheduler.py which makes it possible to execute
> one task once, something that is useful for a long running task. Some
> time ago I was asking about this and you guys said it will be included
> but 1.1b1 still does not have it applied. Any chance this will happen?
The milestone is currently set to 1.1, which means that it will go into
one of the releases leading up to 1.1 final. I'm not sure, if it wil go
into 1.1b2 already. You could speed things up by providing tests
(unfortunately the scheduler module does not have any test yet - see
http://trac.turbogears.org/ticket/1712), or by bugging somebody to
review your code. Also appreciated would be better docstrings and
documentation on the wiki. For the latter you would preferably make a
copy of the current scheduler docs in RoughDocs and make your changes
therr and then this would be copied over when the change is released.
> (The name 'onetime' in 1709 changed to 'single' in 1710 (or the other
> way around) contributing to the confusion already present by the two
> tickets on the same issue. This happened because I created one ticket
> and a reader of the dev list created another. If it will make things
> clearer I can create a final ticket and the two previous can be
> labeled duplicate or closed or something.)
1709 was closed as duplicate, so I regard the patch I attached to 1710
as the current one.
Chris
Christopher Arndt
> If this one is a stable bug fix, maybe we should hassle Webfaction to
> get it added to their control panel? I just set up an app there today
> and had to do all kinds of wacky upgrade stuff as the latest install
> from them is 1.0.4 with no SA or Genshi.
>
> I'm happy to do some hassling if you think this is a good release to
> hassle for.
Let's wait two or three days if any problems are reported and then, if
everything is okay, we would appreciate your hassling :)
Chris
iain duncan
Cool. I think one issue is that to them TG does not include Genshi or SA
or ToscaWidgets. Are we waiting for 1.1 official before 'officially'
bundling those together?
Iain
Florent Aide
>
> On Mon, 2008-15-09 at 23:46 +0200, Christopher Arndt wrote:
>> Let's wait two or three days if any problems are reported and then, if
>> everything is okay, we would appreciate your hassling :)
As Chris just said, if after a few days, 1.0.7 is indeed proved really
stable then we'll appreciate your hassling. And don't forget to ask
them to also bundle your requirements. But we can't require them
ourselves, because it makes no sense to force someone installing in
production to have two orms when he will likely use only one.
> Cool. I think one issue is that to them TG does not include Genshi or SA
> or ToscaWidgets. Are we waiting for 1.1 official before 'officially'
> bundling those together?
>
We don't bundle SA nor Genshi nor TW... We just make it possible to
use them. But you are right that in 1.1 the usage of the first two
components is way easier to find and is promoted by the default
quickstart templates.
Florent.
iain duncan
Thanks for the explanation. So the plan is that a 1.1 install of tg will
set one up with SA+genshi+toscawidgets out of the box?
Iain
Christopher Arndt
- TG 1.1 will require (and install) Genshi
- TG 1.1 quickstart with identity will set up a project to use
SQLAlchemy and when you install the project it will pull SQLAlchemy (but
not before!).
- AFAIR, the plan for TG 1.1 is not provide special support for
ToscaWidgets yet, this will be in TG 1.5. The short-to-mid-term plan is
to replace TG widgets with ToscaWidgets, though. We are open to
contributions (e.g. quickstart templates, making sure there are drop-in
replacements for all TG widgets, etc.) to speed things up.
Chris