Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed3.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.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'true,': 0.05; 'subject:Python': 0.06; '(of': 0.07; 'interpreter.': 0.07; 'remaining': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'runs': 0.10; 'python': 0.11; 'jan': 0.12; 'systems.': 0.12; 'bit).': 0.16; 'development?': 0.16; 'editor,': 0.16; 'itself,': 0.16; 'leakage': 0.16; 'namespace?': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'sockets': 0.16; 'think.': 0.16; 'wrote:': 0.18; 'looked': 0.18; 'not,': 0.20; 'command': 0.22; '>>>': 0.22; 'separate': 0.22; 'header:User- Agent:1': 0.23; 'script': 0.25; 'tracker': 0.26; 'header:X -Complaints-To:1': 0.27; 'van': 0.27; 'header:In-Reply-To:1': 0.27; 'related': 0.29; 'code': 0.31; '>>>>': 0.31; 'default,': 0.31; 'option': 0.32; 'running': 0.33; 'something': 0.35; 'editor': 0.35; 'but': 0.35; 'there': 0.35; 'idle': 0.36; 'opposed': 0.36; 'revert': 0.36; 'integration': 0.37; 'application': 0.37; 'sometimes': 0.38; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'anything': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'remove': 0.60; 'most': 0.60; 'received:173': 0.61; 'connecting': 0.64; 'kept': 0.65; 'within': 0.65; 'advantages': 0.68; 'respect': 0.70; 'below.': 0.71; 'received:fios.verizon.net': 0.84 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: Editor for Python Date: Wed, 08 Jan 2014 20:51:01 -0500 References: <3bfd7f87@news.airtel.net> <6b9049ab-e168-4f92-9526-edcaf806d2cd@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-173-75-254-207.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: 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: 33 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1389232278 news.xs4all.nl 2853 [2001:888:2000:d::a6]:35673 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:63553 On 1/8/2014 7:19 PM, Emile van Sebille wrote: > On 1/8/2014 3:46 PM, Terry Reedy wrote: >> On 1/8/2014 3:56 PM, Emile van Sebille wrote: >>> On 1/8/2014 12:47 PM, Terry Reedy wrote: >>> >>>> For a Python editor, as opposed to a general code editor, the Idle >>>> editor works pretty well and has some advantages with respect to >>>> integration with the interpreter. >>> >>> While true, ISTM in the past there have been 'leakage' related issues >>> with idle -- are those no longer a concern? Almost not, see below. >> I have looked through most of the Idle issues on the tracker but do not >> remember anything about 'leakage' (of memory?) > > Of names I think. > > As I recall it had something to do with both idle and the application > running in the same namespace? So the leakage was from within idle > affecting the running of the script under development? By default, Idle runs user code in a separate process from the Idle process itself, and has for several years. There is a command line option to revert to the old way (user code in the same process). Some of us would like to remove that option (and simplify the remaining code a bit). This option is kept mainly because connecting to the separate process via sockets sometimes fails on some systems. -- Terry Jan Reedy