Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Terry Reedy <tjreedy@udel.edu>
Subject: Re: Under what kind of situation, time.sleep(n) would sleep much longer than n seconds?
Date: Thu, 19 Jun 2014 22:33:54 -0400
References: <713f4189-5ffe-492d-9c7d-447bb4b4928a@googlegroups.com> <mailman.11114.1403087670.18130.python-list@python.org> <4d7c474a-b88e-4dea-b74c-ed34f4969310@googlegroups.com> <mailman.11128.1403134697.18130.python-list@python.org> <lnu2sb$r3d$1@dont-email.me> <CAPTjJmr+rcZKeYg8T5TEQ=+WmFhgXTPY86n6GaMK=g9B-MX5Mw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
In-Reply-To: <CAPTjJmr+rcZKeYg8T5TEQ=+WmFhgXTPY86n6GaMK=g9B-MX5Mw@mail.gmail.com>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.11159.1403231653.18130.python-list@python.org>
Lines: 48
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:73443

On 6/19/2014 3:42 AM, Chris Angelico wrote:
> On Thu, Jun 19, 2014 at 5:18 PM, Christian Gollwitzer <auriocus@gmx.de> wrote:

>> My advice:
>>
>> 1) First try parsing the command line. (Example: All Unix tools)
>>
>> 2) If you require more interaction and maybe state preservation, just write
>> a couple of functions and run it in IPython (Example: SciPy)
>>
>> 3) Use a real GUI framework
>>
>> It turns out, that 3) is actually not only easier to use, but often easier
>> to write than 1)
>
> I disagree. It may not be the *best* console UI, but it's not as bad
> as you think. Yes, what I wrote was a massive oversimplification, but
> compare this:
>
> https://github.com/Rosuav/runningtime/blob/master/runningtime.py#L44
>
> That's a simple, straight-forward UI. If you put the .py file onto
> your desktop and double-click it, you'll see a series of prompts, and
> this works on Windows, OS/2, probably Mac OS, and quite a few Linux
> desktops. (Although I didn't put a shebang on that file, so it might
> not work on your typical Linux.) How do you make something that
> provides command line arguments to a double-clicked-on icon? Different
> for every platform. (And seldom as easy as it is on OS/2.) If you run
> that in a terminal, you'll see a series of prompts, and it works on
> probably every Python implementation EVER. If you pull it up in IDLE,
> it'll probably work there too, although I haven't tried it.

Most any* console script runs fine** in Idle once you load it into the 
editor and press F5. Prompts and prints go the shell window (default 
blue on white) and input comes from the same (default black on white).

* I said most because there must be exceptions, but have no 
characterization.

** Better than the windows console in some respects.

I hope that by the end of the summer, the requirement to load in the 
editor will be gone. (Run F5 saves to a file anyway for actual 
execution.) There should also be an option to put output in a new window.

-- 
Terry Jan Reedy