Turbogears2 migration: paging failures in changelog

[Thomas De Schampheleire]

Mads, Alessandro, all,

On Mon, Jul 18, 2016 at 11:47 PM, Mads Kiilerich <mads at kiilerich.com> wrote:
> On 07/18/2016 09:27 PM, Thomas De Schampheleire wrote:
>>
>>
>> Can you clarify in more detail how you set up your virtualenv?
>> I used 'pip install -e .' now, when I look in the virtualenv I do see
>> .py files for e.g. routes, webhelpers, ... Still I am not seeing such
>> a traceback. That missing piece of information is crucial in analyzing
>> this and other problems, so I really want to understand what is
>> different between your setup and mine.
>
>
> I can reproduce with:
>
> hg up -cr a223a7c4f0ab
> hg purge --all
> virtualenv .hg/venv
> . .hg/venv/bin/activate
> pip install mercurial
> python setup.py develop
> cp ../kallithea.db .
> paster serve development.ini
> firefox http://127.0.0.1:5000/hg/changelog
>
> - and I get a nice stack trace on stdout from the paster serve process.
>

Thanks to these detailed instructions, I was able to determine the
difference. I was testing with test.ini, not with development.ini, the
major difference between both is that debug mode (set debug = X) is
set to true in development.ini, but to false in test.ini. Under
Pylons, 'set debug' purely controls interactive debugging in the
browser. When false, the traceback is shown on the console. When true,
it is shown in the browser.
Under Turbogears (at least in the current interaction with it), 'set
debug = false' does not even show a traceback on the console. With
'set debug = true', the traceback is always shown on the console. If
'backlash' is installed, the interactive debugging is also enabled in
the browser.

Alessandro, is it intentional that no traceback is shown on the
console with 'set debug = false' ? I did not find references to that
in the documentation.

Slightly related: looking at the tg2example development.ini file,
there is just one 'debug' setting under the [DEFAULT] section.
In Kallithea, in development.ini, there is a 'debug = true', 'pdebug =
false' under [DEFAULT] and 'set debug = true' under '[app:main]'. What
do each of these settings control? Should one or more of them be
removed? Is there a difference between Pylons and Turbogears2 here?

Thanks,
Thomas