I thought I did, but when I checked today it seems I've screwed up and
edited logging/__init__.py in 2.4 and tested with 2.3
So after fixing it in the correct place, it works nicely..
--
http://mail.python.org/mailman/listinfo/python-list
simon.dahlbacka gmail.com gmail.com> writes:
>
> I tried moving the import traceback to the start of the file
> (logging/__init__.py) but that did not seem to have any effect?
> I suppose the fix was in version 1.26 in cvs?
>
Did you do this for all cases in __init__.py? You may also need to
I tried moving the import traceback to the start of the file
(logging/__init__.py) but that did not seem to have any effect?
I suppose the fix was in version 1.26 in cvs?
--
http://mail.python.org/mailman/listinfo/python-list
Simon Dahlbacka gmail.com> writes:
This is a known problem, and a patch was put into CVS. I would suggest that you
either check out the version from CVS, or move the "import traceback" to the top
of the module.
The problem is caused by a threading deadlock which occurs when an importer
tries to
I probably did not mention it, but I've used traceback module in other
places, and it works fine.
We've been planning to upgrade to 2.4 but unfortunately I cannot do
that right now, and no, I have not messed with any other system modules.
--
http://mail.python.org/mailman/listinfo/python-list
Simon Dahlbacka wrote:
print sys.modules["traceback"]
import traceback
print "Hello World"
sys.stdout.flush()
just renders: in the
console, and no "Hello World"
Works fine on Python 2.4 for Windows.
I'm running out of ideas what to try next, so suggestions/ideas appreciated!
That's a very strange
