Chris McDonough wrote:
It's just not possible to upgrade components of every configuration.
Sometimes you just need to live with some specific configuration for a
while. It's not really a bad thing to have a known-working
configuration, even if it's a little old.
+sys.maxint
If we turned t
--On 14. Juni 2006 05:40:15 -0400 Chris McDonough <[EMAIL PROTECTED]> wrote:
Given the above, if there's not total opposition to this, I'd volunteer
to make these log calls into warnings during bugday tomorrow on the 2.8,
2.9, and 2.10 branches. It might be a good idea to turn all deprecat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 14, 2006, at 4:36 AM, Andreas Jung wrote:
--On 14. Juni 2006 10:25:57 +0200 thomas desvenain
<[EMAIL PROTECTED]> wrote:
2006/6/13, Chris McDonough <[EMAIL PROTECTED]>:
I suppose a log call is fine.
I *really* like these messages, beca
--On 14. Juni 2006 10:25:57 +0200 thomas desvenain
<[EMAIL PROTECTED]> wrote:
2006/6/13, Chris McDonough <[EMAIL PROTECTED]>:
I suppose a log call is fine.
I *really* like these messages, because they catch a lot of my own
boneheaded security declaration errors. But for ones that aren't
a
2006/6/13, Chris McDonough <[EMAIL PROTECTED]>:
I suppose a log call is fine.
I *really* like these messages, because they catch a lot of my own
boneheaded security declaration errors. But for ones that aren't
actually "real" problems (like the ones shown by the OP), it would be
nice to be able
I suppose a log call is fine.
I *really* like these messages, because they catch a lot of my own
boneheaded security declaration errors. But for ones that aren't
actually "real" problems (like the ones shown by the OP), it would be
nice to be able to filter them away at startup, especially
Indeed they are logging.getLogger("Init") calls (from App/
class_init.py).
Why change that? They're perfectly fine in the event log.
Florent
On 13 Jun 2006, at 23:08, Chris McDonough wrote:
Not out of the box.
Egads, I think you're right. These aren't actual warnings, are
they? They'r
Not out of the box.
Egads, I think you're right. These aren't actual warnings, are
they? They're log calls. That should be changed.
- C
Actually, there is a way, but it's a bit heavy-handed and
imprecise. In zope.conf, do (untested):
action ignore
message .*has a security d
On Jun 13, 2006, at 11:05 AM, Florent Guillaume wrote:
thomas desvenain wrote:
i mean i would like to filter warning/error messages that appears
in console
when starting zope server or debugger
in order to ignore those i'm not interested with for the moment
for instance :
[EMAIL PROTECTED] t
Florent Guillaume wrote:
thomas desvenain wrote:
i mean i would like to filter warning/error messages that appears in
console
when starting zope server or debugger
in order to ignore those i'm not interested with for the moment
for instance :
[EMAIL PROTECTED] tests]# /zope/test/bin/zopectl d
thomas desvenain wrote:
i mean i would like to filter warning/error messages that appears in
console
when starting zope server or debugger
in order to ignore those i'm not interested with for the moment
for instance :
[EMAIL PROTECTED] tests]# /zope/test/bin/zopectl debug
Starting debugger (th
11 matches
Mail list logo
