I upgraded to 2.7b3, and it looks quite solid!
I have one problem, though: I can't find the full tracebacks that
include __traceback_info__ anywhere!
I used to start up Zope in debug mode, so I'd get everything sent to
stdout. Now, stdout just contains some startup stuff; doesn't even
contain
I upgraded to 2.7b3, and it looks quite solid!
I have one problem, though: I can't find the full tracebacks that
include __traceback_info__ anywhere!
You can add this to your standard_error_message:
dtml-if error_tb
dtml-var error_tb
/dtml-if
--
Santi Camps
Bjorn Stabell wrote at 2003-12-21 23:49 +0800:
I upgraded to 2.7b3, and it looks quite solid!
I have one problem, though: I can't find the full tracebacks that
include __traceback_info__ anywhere!
They are not in http://yourZope/error_log?
--
Dieter
The extant import Zope; app = Zope.app() dance to get a hold of the
Zope root object stopped working long ago on the 2.7 branch and HEAD due
to the new configuration machinery, which implies that users be explicit
about configuration settings rather than allowing Zope to guess.
Up til now, the
Chris McDonough wrote
Code which used to do:
import Zope
app = Zope.app()
Will need to do this under 2.7b4+:
import Zope
Zope.configure('/path/to/configfile')
app = Zope.app()
Can we get an exception in the first case that states something like
No config file, use
On Sun, 2003-12-21 at 19:43, Anthony Baxter wrote:
Can we get an exception in the first case that states something like
No config file, use Zope.configure('configfile')?
I think that can be arranged. Or something that smells like it
anyway...
___
Dieter:
Bjorn Stabell wrote at 2003-12-21 23:49 +0800:
I upgraded to 2.7b3, and it looks quite solid!
I have one problem, though: I can't find the full tracebacks that
include __traceback_info__ anywhere!
They are not in http://yourZope/error_log?
No, the error, UnicodeError, doesn't
