Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.011 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'that?': 0.05; 'from:addr:ethan': 0.09; 'from:addr:stoneleaf.us': 0.09; 'from:name:ethan furman': 0.09; 'message-id:@stoneleaf.us': 0.09; 'subject:using': 0.09; '~ethan~': 0.09; 'subject:skip:m 10': 0.16; 'subject:when': 0.16; 'exception': 0.16; 'so.': 0.16; 'wrote:': 0.18; 'not,': 0.20; 'issue.': 0.22; 'header:User-Agent:1': 0.23; 'certainly': 0.24; 'this:': 0.26; 'header:In-Reply-To:1': 0.27; 'bug?': 0.31; 'anyone': 0.31; 'skip:m 30': 0.32; 'doing': 0.36; 'charset:us-ascii': 0.36; 'subject:?': 0.36; 'should': 0.36; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'anything': 0.39; 'to:addr:python.org': 0.39; 'how': 0.40; 'new': 0.61; 'john': 0.61; 'received:173': 0.61; 'received:64.5': 0.84; 'ultimate': 0.93; 'obtained': 0.96 Date: Thu, 21 Nov 2013 14:32:08 -0800 From: Ethan Furman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Traceback when using multiprocessing, less than helpful? References: <9eb71131-7ca0-4a21-a8f3-98371ee8787e@googlegroups.com> <46e03756-a242-4cdd-a5c0-30fcff34c98c@googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator3304.hostgator.com X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - stoneleaf.us X-BWhitelist: no X-Source-IP: 173.12.184.233 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: ([173.12.184.233]) [173.12.184.233]:39253 X-Source-Auth: ethan+stoneleaf.us X-Email-Count: 1 X-Source-Cap: dG9idWs7dG9idWs7Z2F0b3IzMzA0Lmhvc3RnYXRvci5jb20= X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 19 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1385073129 news.xs4all.nl 15882 [2001:888:2000:d::a6]:35042 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:60177 On 11/21/2013 01:49 PM, John Ladasky wrote: > > So now, for anyone who is still reading this: is it your > opinion that the traceback that I obtained through > multiprocessing.pool._map_async().get() SHOULD have allowed > me to see what the ultimate cause of the exception was? It would certainly be nice. > I think so. Is it a bug? Should I request a bugfix? How > do I go about doing that? Check out bugs.python.org. Search for multiprocessing and tracebacks to see if anything is already there; if not, create a new issue. -- ~Ethan~