Chris Angelico <ros...@gmail.com> writes:
> On Wed, Jun 4, 2014 at 12:30 PM, Nikolaus Rath <nikol...@rath.org> wrote:
>> I've instrumented one of my unit tests with a conditional
>> 'pdb.set_trace' in some circumstances (specifically, when a function is
>> called by a thread other than MainThread).
>
> I think the likelihood of this being an issue with interactive
> debugging and threads is sufficiently high that you should avoid
> putting the two together, at least until you can verify that the same
> problem occurs without that combination.
Here's stacktrace as obtained by traceback.print_stack():
tests/t1_backends.py:563: test_extra_data[mock_s3c-zlib] PASSED
tests/t1_backends.py:563: test_extra_data[mock_s3c-bzip2] PASSED
======================== 87 tests deselected by '-kextra'
=========================
=============== 5 passed, 1 skipped, 87 deselected in 0.65 seconds
================
File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/common.py", line 853,
in close
self.fh.close()
File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/s3c.py", line 691, in
close
traceback.print_stack(file=sys.stdout)
something is wrong
File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/common.py", line 853,
in close
self.fh.close()
File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/s3c.py", line 691, in
close
traceback.print_stack(file=sys.stdout)
something is wrong
File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/common.py", line
1050, in close
self.fh.close()
File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/s3c.py", line 691, in
close
traceback.print_stack(file=sys.stdout)
Still no context before the ominous close() call. I'm very confused.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
https://mail.python.org/mailman/listinfo/python-list
