Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #56719 > unrolled thread

Re: Problem in Multiprocessing module

Started byDennis Lee Bieber <wlfraed@ix.netcom.com>
First post2013-10-11 21:50 -0400
Last post2013-10-11 21:50 -0400
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.


Contents

  Re: Problem in Multiprocessing module Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-10-11 21:50 -0400

#56719 — Re: Problem in Multiprocessing module

FromDennis Lee Bieber <wlfraed@ix.netcom.com>
Date2013-10-11 21:50 -0400
SubjectRe: Problem in Multiprocessing module
Message-ID<mailman.1026.1381542615.18130.python-list@python.org>
On Fri, 11 Oct 2013 18:58:44 -0400, Terry Reedy <tjreedy@udel.edu>
declaimed the following:


>
>so it seems that we need to look at the _Condition methods acquire, 
>release, and wait. (The first two are lock methods
>         self.acquire = lock.acquire
>         self.release = lock.release
>). However, this seems wrong because self._cond has no reference to self 

	Pardon?

	self._cond (in the parent) is an instance object. Therefore the parent
calls supply "self._cond" AS the "self" argument to the lower level
methods.

-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web