page 354, Section 18.1.3, 3rd para

[dundeemt]

On page 354, Section 18.1.3, 3rd para, "-- all you have to do is delete
dev.cfg; TurboGears will automatically start using your production
configuration." is incorrect. At least with v1.0b1 and newer.

Whether or not prod.cfg is looked at depends on the existence of
setup.py. There is code in startup-ProjectName.py and util.py in the
libs that looks for setup.py. It caused a fair amount of my saturday
figuring out where in the code the decision was being made -- I did get
to meet a portion of the tg code -- not quite how I intended though<g>.

testing your prod.cfg is as simple as passing it as the argument to
startup-ProjectName.py prod.cfg

[Mark Ramm]

I'll take a look at this section of the book and figure out what
happened, but you are right, and this is absolutely something that
should be on the errata pages right away.

If you have a chance you might want to try adding it to the new wiki
page I'm testing out for "user contributed errata"

http://groups.google.com/group/tgbook/web

If this works out, I may link too it from the book website, and
announce it on the main mailing list.

--Mark

--
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

[mark.mch...@gmail.com]

I almost got the right link, this one should take you directly to the
errata page:

http://groups.google.com/group/tgbook/web/tg-errata

On Jan 23, 11:22 pm, "Mark Ramm" <mark.mchristen...@gmail.com> wrote:
> I'll take a look at this section of the book and figure out what
> happened, but you are right, and this is absolutely something that
> should be on the errata pages right away.
>
> If you have a chance you might want to try adding it to the new wiki
> page I'm testing out for "user contributed errata"
>
> http://groups.google.com/group/tgbook/web
>
> If this works out, I may link too it from the book website, and
> announce it on the main mailing list.
>
> --Mark
>