Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!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.003 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'from:addr:yahoo.co.uk': 0.04; 'cpython': 0.05; 'mrab': 0.05; 'subject:Python': 0.06; 'amounts': 0.07; 'interpreter.': 0.07; 'tkinter': 0.07; "ain't": 0.09; 'cursor': 0.09; 'forcing': 0.09; 'insertion': 0.09; 'lawrence': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'contribute': 0.11; 'python': 0.11; 'language.': 0.14; 'windows': 0.15; '*why*': 0.16; 'chris,': 0.16; 'displaying': 0.16; 'esp': 0.16; 'letting': 0.16; 'marker': 0.16; 'raging': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'think?': 0.16; 'unchanged': 0.16; 'thursday,': 0.16; 'language': 0.16; 'fix': 0.17; 'wrote:': 0.18; 'command': 0.22; '>>>': 0.22; 'code,': 0.22; 'shell': 0.22; 'header:User-Agent:1': 0.23; 'hours,': 0.24; '---': 0.24; 'source': 0.25; 'primary': 0.26; 'skip:" 20': 0.27; 'header:X-Complaints-To:1': 0.27; 'header:In- Reply-To:1': 0.27; 'chris': 0.29; 'leave': 0.29; 'room': 0.29; 'experiences': 0.30; 'especially': 0.30; "i'm": 0.30; 'code': 0.31; 'software,': 0.31; 'url:wiki': 0.31; 'accidentally': 0.31; 'piece': 0.31; 'url:wikipedia': 0.31; 'run': 0.32; 'quite': 0.32; 'text': 0.33; 'open': 0.33; 'maybe': 0.34; 'could': 0.34; 'problem': 0.35; 'display': 0.35; 'editor': 0.35; 'johnson': 0.35; 'one,': 0.35; 'plans': 0.35; 'but': 0.35; 'there': 0.35; 'idle': 0.36; 'next': 0.36; 'method': 0.36; 'useful': 0.36; 'url:org': 0.36; 'should': 0.36; 'half': 0.37; 'area': 0.37; 'work?': 0.38; 'to:addr:python-list': 0.38; 'issue': 0.38; 'that,': 0.38; 'does': 0.39; 'though,': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'space': 0.40; 'how': 0.40; 'even': 0.60; 'easy': 0.60; 'free': 0.61; 'new': 0.61; 'entire': 0.61; 'viruses': 0.61; 'skip:* 10': 0.61; 'times': 0.62; "you've": 0.63; 'protection': 0.63; 'hear': 0.63; 'such': 0.63; 'july': 0.63; 'visit': 0.64; 'our': 0.64; 'more': 0.64; 'between': 0.67; 'close': 0.67; 'hang': 0.67; 'believe': 0.68; 'yes': 0.68; 'antivirus': 0.68; 'press': 0.70; 'glad': 0.83; 'alone,': 0.84; 'ashamed': 0.84; 'fat': 0.84; 'semi': 0.84; 'years!': 0.84; 'received:89': 0.85; 'rick': 0.93; 'scene': 0.93; 'suffering': 0.93 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Mark Lawrence Subject: Re: Python 3 is killing Python Date: Fri, 18 Jul 2014 17:22:04 +0100 References: <87zjga4j4v.fsf@elektro.pacujo.net> <53c57bae$0$9505$c3e8da3$5496439d@news.astraweb.com> <87iomy4ciy.fsf@elektro.pacujo.net> <53c5f6dc$0$9505$c3e8da3$5496439d@news.astraweb.com> <87egxl4zq8.fsf@elektro.pacujo.net> <53c73ff0$0$29897$c3e8da3$5496439d@news.astraweb.com> <9ef930a0-5a41-4a20-a13a-003c9e8246fe@googlegroups.com> <53C94157.9060500@mrabarnett.plus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: host-89-240-174-91.as13285.net User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 In-Reply-To: <53C94157.9060500@mrabarnett.plus.com> X-Antivirus: avast! (VPS 140718-0, 18/07/2014), Outbound message X-Antivirus-Status: Clean 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: 79 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1405700539 news.xs4all.nl 2896 [2001:888:2000:d::a6]:36407 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:74758 On 18/07/2014 16:46, MRAB wrote: > On 2014-07-18 04:37, Rick Johnson wrote: >> On Thursday, July 17, 2014 9:15:15 PM UTC-5, Chris Angelico wrote: >>> For myself, though, I completely do not use the editor half of >>> [IDLE]; but >>> it's spectacularly useful (with limitations) as my primary interactive >>> interpreter. >> >> Yes Chris, i also think that the IDLE shell is "spectacular" >> when i'm using it, especially when i press >> "CONTROL+LEFT_ARROW" and the insertion cursor lands *BEHIND* >> the start of the interactive command marker " >>>", an >> area where key presses are not allowed, so *NOW* I must press >> "CONTROL+RIGHT_ARROW" three times to get to my destination! >> >> I'm also just "gushing with exuberance" when i open a new >> block and i get *EIGHT SPACE INDENTION*! >> >> And I get a raging semi each time IDLE hangs between run >> sessions when i'm editing Tkinter code, yes Chris, I GET A >> BIG FAT ERECTION! Sometimes, when it does not go away >> after four hours, i have to visit the local emergency room >> and take some pills. >> >> THAT'S HOW MUCH I JUST *LOVE* THIS CRAPPY SOFTWARE CHRIS! >> >> I'M SO GLAD WE CAN SHARE THESE "WONDERFUL" EXPERIENCES TOGETHER! >> >> MAYBE NEXT WE CAN RE-INACT THE LAST SCENE OF ROMEO AND JULIETTE? >> >>> [...] The only problem I have with it is that blatting >>> ridiculous amounts of text to the console can take a very >>> long time, esp on Windows. If I accidentally display a >>> large object when I thought I was displaying a small one, >>> it'll hang for quite a while, churning through something, >>> and it's not easy to see why or to halt it. But I suspect >>> that's more of a Windows and/or Tk issue than an Idle one. >> >> The *PROBLEM* is that user has no method of "undo-ing" an >> accidental display of huge amounts of data , forcing the >> user to close and then re-open the entire software -- can >> you understand now *WHY* i complain about this software? >> >> This is *EMBARRASSING*, and you should *ALL* be ashamed >> that, not only does Python include such an amateurish piece >> of crap software, but it has been there for years! >> >> UNCHANGED FOR YEARS!!! >> > I'm sorry to hear that you've been suffering all these years. If only > there were a way to fix it. > > Here's a suggestion for the Python community: how about opening up the > source code and letting people contribute fixes? We could call this > "open source". > > We could even open the source for CPython itself! Could that work? > > What do you think? > That plan is so cunning it makes Baldrick's cunning plans look good :) http://en.wikipedia.org/wiki/Baldrick Actually I believe we should just leave things alone, if it ain't broke, don't fix it. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com