Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #53752
| References | <ca7ea9d1-4dad-4a30-97b2-ad8536a1860b@googlegroups.com> <mailman.107.1378420122.5461.python-list@python.org> <9d088493-8224-4a48-a2d3-5b7207dc8947@googlegroups.com> |
|---|---|
| Date | 2013-09-06 13:00 +1000 |
| Subject | Re: Multiprocessing / threading confusion |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.111.1378436451.5461.python-list@python.org> (permalink) |
On Fri, Sep 6, 2013 at 9:34 AM, Paul Pittlerson <menkomigen6@gmail.com> wrote: > On Friday, September 6, 2013 1:28:39 AM UTC+3, mar...@python.net wrote: > >> Also you can't (and shouldn't) depend on the time that __del__ gets >> called. It can get called at any time, in any order and sometimes not >> at all.* > > Wow I did not know that! I was counting on that it reliably gets called when the object is destroyed. Even that isn't technically reliable, though in CPython, objects will usually be __del__'d promptly as long as they're not in reference cycles. But the main problem here is that the destruction of the object has nothing to do with the ending of the thread or process; the object will hang around for as long as the caller might want it. You'll want to put your "end of process" code at the bottom of run(), I think, unless there's some other place for it. ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Multiprocessing / threading confusion Paul Pittlerson <menkomigen6@gmail.com> - 2013-09-05 12:27 -0700
Re: Multiprocessing / threading confusion "marduk@python.net" <marduk@python.net> - 2013-09-05 18:28 -0400
Re: Multiprocessing / threading confusion Paul Pittlerson <menkomigen6@gmail.com> - 2013-09-05 16:34 -0700
Re: Multiprocessing / threading confusion Chris Angelico <rosuav@gmail.com> - 2013-09-06 13:00 +1000
Re: Multiprocessing / threading confusion Chris Angelico <rosuav@gmail.com> - 2013-09-06 08:46 +1000
Re: Multiprocessing / threading confusion Paul Pittlerson <menkomigen6@gmail.com> - 2013-09-05 17:03 -0700
Re: Multiprocessing / threading confusion Piet van Oostrum <piet@vanoostrum.org> - 2013-09-05 23:54 -0400
Re: Multiprocessing / threading confusion Piet van Oostrum <piet@vanoostrum.org> - 2013-09-06 00:28 -0400
Re: Multiprocessing / threading confusion Paul Pittlerson <menkomigen6@gmail.com> - 2013-09-06 11:27 -0700
Re: Multiprocessing / threading confusion Skip Montanaro <skip@pobox.com> - 2013-09-06 13:53 -0500
Re: Multiprocessing / threading confusion Dave Angel <davea@davea.name> - 2013-09-06 20:34 +0000
Re: Multiprocessing / threading confusion Piet van Oostrum <piet@vanoostrum.org> - 2013-09-06 17:15 -0400
csiph-web