Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #72810 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2014-06-06 12:30 +1000 |
| Last post | 2014-06-06 12:30 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Missing stack frames? Chris Angelico <rosuav@gmail.com> - 2014-06-06 12:30 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-06-06 12:30 +1000 |
| Subject | Re: Missing stack frames? |
| Message-ID | <mailman.10802.1402021828.18130.python-list@python.org> |
On Fri, Jun 6, 2014 at 12:16 PM, Nikolaus Rath <Nikolaus@rath.org> wrote: > - Is there some way to make the call stack for destructors less confusing? First off, either don't have refloops, or explicitly break them. That'll at least make things a bit more predictable; in CPython, you'll generally see destructors called as soon as something goes out of scope. Secondly, avoid threads when you're debugging a problem! I said this right at the beginning. If you run into problems, the first thing to do is isolate the system down to a single thread. Debugging is way easier without threads getting in each other's ways. ChrisA
Back to top | Article view | comp.lang.python
csiph-web