Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #52273
| From | random832@fastmail.us |
|---|---|
| References | <5205435D.5090704@Gmail.com> <520546A2.50900@mrabarnett.plus.com> <52055478.2080704@Gmail.com> |
| Subject | Re: Python3 Multiprocessing |
| Date | 2013-08-09 16:54 -0400 |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.408.1376081681.1251.python-list@python.org> (permalink) |
On Fri, Aug 9, 2013, at 16:43, Devyn Collier Johnson wrote: > Thanks MRAB! That is easy. I always (incorrectly) thought the join() > command got two threads and made them one. I did not know it made the > script wait for the threads. What you're missing is the fact that the main thread [i.e. the one running "the script", and that waits for the thread you call the method on] is, well, a thread. So, you start with two threads [the main thread and the jobs1 thread, for example], and end up with one [the main thread]. This is why it's called join.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Python3 Multiprocessing random832@fastmail.us - 2013-08-09 16:54 -0400
csiph-web