Dieter Maurer wrote:
And I posted a ZConfig extension that allows to read the environment
(thus using environment variables in the configuration file).
Did you talk to the ZConfig maintainer about merging this?
I know he wasn't keen but I think it's great extra functionality to have...
Chris
Dieter Maurer wrote:
-self._log.error(msg)
+self._log.error(msg,exc_info=True)
raise ConnectionStateError(msg)
I mind -- the change is stupid:
Because you are not in an exception handler, "exc_info=True"
cannot provide meaningful information -- there is
Tim Peters wrote:
ZEO's got rather noisy in Zope 2.8 :-S
Offhand I didn't find any message logged at INFO level by ClientStorage.py
in ZODB 3.4 (Zope 2.8) that wasn't also logged at INFO level by
ClientStorage.py in ZODB 3.2 (Zope 2.7). What specifically do you find
noisier under 2.8 than unde
Dieter Maurer wrote:
def p64(v):
"""Pack an integer or long into a 8-byte string"""
Yes, but for that to be meaningful, you have to know that:
- 0xSomething is an integer or long (it read "hex number" in my head"
- oids are 8-byte strings
Neither of things that sit in my brain :-(
Chris Withers wrote:
Dieter Maurer wrote:
-self._log.error(msg)
+self._log.error(msg,exc_info=True)
raise ConnectionStateError(msg)
I mind -- the change is stupid:
Because you are not in an exception handler, "exc_info=True"
cannot provide meaningful
On 10/25/05, Chris Withers <[EMAIL PROTECTED]> wrote:
> Dieter Maurer wrote:
> >>>def p64(v):
> >>>"""Pack an integer or long into a 8-byte string"""
> >>
> >>Yes, but for that to be meaningful, you have to know that:
> >>
> >>- 0xSomething is an integer or long (it read "hex number" in
Jeremy Hylton wrote:
On 10/25/05, Chris Withers <[EMAIL PROTECTED]> wrote:
Dieter Maurer wrote:
def p64(v):
"""Pack an integer or long into a 8-byte string"""
Yes, but for that to be meaningful, you have to know that:
- 0xSomething is an integer or long (it read "hex number" in my
[Chris Withers]
>>> ZEO's got rather noisy in Zope 2.8 :-S
[Tim Peters]
>> Offhand I didn't find any message logged at INFO level by
>> ClientStorage.py in ZODB 3.4 (Zope 2.8) that wasn't also logged at INFO
>> level by ClientStorage.py in ZODB 3.2 (Zope 2.7). What specifically do
>> you find noi
Florent Guillaume wrote:
I guess I'm looking for a show_stack option...
import traceback; traceback.print_stack()
Yes thankyou, my egg sucking is quite proficient ;-)
Tim, how would I go about getting one of those added to Python?
(It's not much of a code change, but the process of getting
[Tim Peters]
>> You found ZODB.utils, which was a sensible place to look. I don't
>> really understand how you found ZODB.utils but didn't manage to find
>> p64, because p64 is the first function in the file.
[Chris Withers]
> Because its name means nothing to me...
I'll buy that ;-) But by the
[Chris Withers]
...
> The alias I suggested is purely to mirror that of the oid_repr function,
Except p64 isn't oid_repr's inverse, so an alias for p64 suggesting it _was_
oid_repr's inverse would be confusing, because it would be lying. There is
no inverse for oid_repr, and there isn't a need fo
[Chris Withers]
> I'd like to be able to do:
>
> logger.info('blah',show_stack=True)
Well, you can't ;-)
It's not hard to roll yourself, so I expect (but don't know) that the
logging module's author would resist adding it. For example,
import traceback
from cStringIO import StringIO
...
..
Dear ZODB developers
I am not sure whether ZODB is the right thing to use for my needs. So,
what do I want?
I have a number of threaded objects that have a context as a separate
entity. The object and context need to be separated to allow for the
threads to run asynchronously while their con
13 matches
Mail list logo
