Hi,
while working on something in my current project I have made several
improvements to the logging package in Python, two of them are worth
mentioning:
1. addition of a logging record field %(function)s, which results in
the name
of the entity which logged the record. My version even deduces the
oken?
I get similar results for larger/more complex pieces of code.
Thanks in advance,
Rotem
--
http://mail.python.org/mailman/listinfo/python-list
ll, for now in pydb CVS, I've worked around this by checking.
>
> [EMAIL PROTECTED] (R. Bernstein) writes:
> > "Rotem" <[EMAIL PROTECTED]> writes:
>
> > > Hi,
>
> > > Maybe I'm repeating a previous post (please correct me if I am).
> * comp.lang.python is not the place to file bug reports
Agreed
> * more detail is needed that what's been given so far
Agreed. I will investigate further when I get a chance and determine if
it's a problem on my end.
Thanks a lot!
--
http://mail.python.org/mailman/listinfo/python-list
while
fork() was called will deadlock.
Due to these oddities I was wondering if it would be better to extract
the above import line from the execvpe call, to prevent lock
acquisition attempts in such cases.
I'd appreciate any opinions you might have on the subject.
Thanks in advance,
Another workaround could be re-assigning a new lock to import_lock
(such a thing is done with the global interpreter lock) at
PyOS_AfterFork or pthread_atfork.
--
http://mail.python.org/mailman/listinfo/python-list
eback frame points
doesn't do anything special - it just catches an exception, without
saving the exception itself and/or traceback anywhere.
Before I dive into the Python code itself - does anyone have any idea
what can cause this?
Thanks,
Rotem
--
http://mail.python.org/mailman/listinfo/python-list
