Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!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.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'subject:error': 0.03; 'smallest': 0.07; 'tool,': 0.07; 'functioning': 0.09; 'subject:using': 0.09; 'things,': 0.09; 'yeah,': 0.09; 'cc:addr :python-list': 0.11; 'bug': 0.12; 'thread': 0.14; 'created.': 0.16; 'definition.': 0.16; 'discussion.': 0.16; 'fine.': 0.16; 'fork': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'ought': 0.16; 'subject:distribution': 0.16; 'thread,': 0.16; 'demonstrate': 0.16; 'thanks,': 0.17; 'wrote:': 0.18; 'finished': 0.19; 'command': 0.22; 'cc:addr:python.org': 0.22; 'error': 0.23; 'mind.': 0.24; 'subject:python.org': 0.24; 'cc:2**0': 0.24; 'post': 0.26; 'certain': 0.27; 'header:In-Reply- To:1': 0.27; 'point': 0.28; 'function': 0.29; 'wondering': 0.29; 'external': 0.29; 'am,': 0.29; 'possibility': 0.29; 'wonder': 0.29; 'message-id:@mail.gmail.com': 0.30; "i'm": 0.30; 'code': 0.31; 'getting': 0.31; 'piece': 0.31; 'trivial': 0.31; 'worked': 0.33; 'could': 0.34; 'problem': 0.35; 'problem.': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'really': 0.36; 'doing': 0.36; "i'll": 0.36; 'error.': 0.37; 'being': 0.38; 'reported': 0.39; 'though,': 0.39; 'unable': 0.39; 'how': 0.40; 'signal': 0.60; 'new': 0.61; 'further': 0.61; 'here': 0.66; 'discovered': 0.83; 'sometimes.': 0.84; 'whereby': 0.84; 'to:none': 0.92 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type:content-transfer-encoding; bh=/0ihk8evzRQmlRiKMBg8B3uLKlELDQs5Xip238GiArA=; b=spiiYZ4qIKeeywD5bLKghYwT3nF+uO4M2HlKD9mAB3TSy4LWmBqmxLr6sxLr6yiy6V iZkvGNchLvhOhIFxZL88HbC1v2bqEFu6qArACQnGx2BGFpDnWwYi9ympKHDiaJOw4Z3J LYl5xy4mEfTtdz+gRAJRnSa4GA/Hcg9Fpl79CyyBO4QCIPGBE3WKE1n5Ye/PRACcZZbq 8+MRW7rqlZBlo20HIgZxq2QxWy/4POLMW1cZIlWuPg7se1DZUPLUGw5WvNwWpsMlW/1v 6afYpl2DMZhD8yCeLoL6R057M9te5Ph5ZVPCr0e9CNAgABkP4fSxiLywDlelWoIp9VhB mINA== MIME-Version: 1.0 X-Received: by 10.220.250.203 with SMTP id mp11mr25848876vcb.2.1398726031924; Mon, 28 Apr 2014 16:00:31 -0700 (PDT) In-Reply-To: References: <675725e3-38d2-4d81-bf64-f6d903d4a684@googlegroups.com> Date: Tue, 29 Apr 2014 09:00:31 +1000 Subject: Re: MacOS 10.9.2: threading error using python.org 2.7.6 distribution From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: 28 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1398726034 news.xs4all.nl 2889 [2001:888:2000:d::a6]:34651 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:70700 On Tue, Apr 29, 2014 at 8:50 AM, Matthew Pounsett wrote: > Thanks, I'll keep all that in mind. I have to wonder how much of a probl= em it is here though, since I was able to demonstrate a functioning fork in= side a new thread further up in the discussion. > Yeah, it's really hard to pin down sometimes. I once discovered a problem whereby I was unable to spin off subprocesses that did certain things, but I could do a trivial subprocess (I think I fork/exec'd to the echo command or something) and that worked fine. Turned out to be a bug in one of my signal handlers, but the error was being reported at the point of the forking. > I have a new development that I find interesting, and I'm wondering if yo= u still think it's the same problem. > > I have taken that threading object and turned it into a normal function d= efinition. It's still forking the external tool, but it's doing so in the = main thread, and it is finished execution before any other threads are crea= ted. And I'm still getting the same error. > Interesting. That ought to eliminate all possibility of thread-vs-process issues. Can you post the smallest piece of code that exhibits the same failure? ChrisA