Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!xlned.com!feeder7.xlned.com!newsfeed.xs4all.nl!newsfeed4.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.042 X-Spam-Evidence: '*H*': 0.92; '*S*': 0.00; "'return": 0.09; 'executed': 0.09; 'received:localdomain': 0.11; 'python': 0.11; 'wrote': 0.14; 'wrote:': 0.18; 'code.': 0.18; 'trying': 0.19; 'machine': 0.22; 'header:User-Agent:1': 0.23; 'certainly': 0.24; 'header:In-Reply-To:1': 0.27; "i'm": 0.30; "i'd": 0.34; 'should': 0.36; 'received:76': 0.38; 'machines': 0.38; 'to:addr:python- list': 0.38; 'issue': 0.38; 'pm,': 0.38; 'sure': 0.39; 'to:addr:python.org': 0.39; 'tell': 0.60; "you're": 0.61; 'gelonida': 0.84; 'carlos': 0.91 Date: Mon, 09 Jun 2014 16:07:11 +0100 From: Carlos Anselmo Dias User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: python-list@python.org Subject: Re: embedding ipython kernel in a thread References: <5395B800.3040504@premium-sponsor.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 18 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1402326435 news.xs4all.nl 2846 [2001:888:2000:d::a6]:48153 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:73035 On 06/09/2014 03:55 PM, Gelonida N wrote: > Not sure what you are trying to tell me with attached PHP code. > Hi ... Nothing important I'd write for what you're seeking ... I'm not one Python expert ... just reading fast what you wrote ... it's certainly one interesting issue if you can control that looking at n machines (...) ... depending on the scope and 'return back' to execute what should be executed I'd write ... Instead of looking to one single machine look at n machines(...) Regards, Carlos