Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #57091 > unrolled thread

Error Testing

Started byScott Novinger <scnovinger@gmail.com>
First post2013-10-19 05:23 -0700
Last post2013-10-21 15:29 -0500
Articles 4 on this page of 24 — 12 participants

Back to article view | Back to comp.lang.python


Contents

  Error Testing Scott Novinger <scnovinger@gmail.com> - 2013-10-19 05:23 -0700
    Re: Error Testing Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-19 13:37 +0100
      Re: Error Testing Scott Novinger <scnovinger@gmail.com> - 2013-10-19 06:34 -0700
        Re: Error Testing Chris Angelico <rosuav@gmail.com> - 2013-10-20 00:42 +1100
        Re: Error Testing rusi <rustompmody@gmail.com> - 2013-10-19 09:22 -0700
          Re: Error Testing Chris Angelico <rosuav@gmail.com> - 2013-10-20 09:28 +1100
          Re: Error Testing Ned Deily <nad@acm.org> - 2013-10-19 15:46 -0700
          Re: Error Testing Chris Angelico <rosuav@gmail.com> - 2013-10-20 10:02 +1100
          Re: Error Testing Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-10-20 12:18 -0400
    Re: Error Testing Ned Batchelder <ned@nedbatchelder.com> - 2013-10-19 08:44 -0400
      Re: Error Testing Roy Smith <roy@panix.com> - 2013-10-19 08:57 -0400
        Re: Error Testing Chris Angelico <rosuav@gmail.com> - 2013-10-20 00:04 +1100
        Re: Error Testing Ned Batchelder <ned@nedbatchelder.com> - 2013-10-19 09:07 -0400
          Re: Error Testing Roy Smith <roy@panix.com> - 2013-10-19 09:09 -0400
        Re: Error Testing Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-19 14:19 +0100
    Re: Error Testing Chris Angelico <rosuav@gmail.com> - 2013-10-20 00:01 +1100
    Re: Error Testing David Robinow <drobinow@gmail.com> - 2013-10-19 14:08 -0400
    Re: Error Testing Tim Chase <tim@thechases.com> - 2013-10-19 13:31 -0500
    Re: Error Testing Terry Reedy <tjreedy@udel.edu> - 2013-10-19 15:50 -0400
    What's wrong with Windows Command Prompt (was Re: Error Testing) Terry Reedy <tjreedy@udel.edu> - 2013-10-19 16:35 -0400
    Re: What's wrong with Windows Command Prompt (was Re: Error Testing) Chris Angelico <rosuav@gmail.com> - 2013-10-20 09:15 +1100
    Re: Error Testing Chris Angelico <rosuav@gmail.com> - 2013-10-20 09:20 +1100
    Re: What's wrong with Windows Command Prompt (was Re: Error Testing) David Robinow <drobinow@gmail.com> - 2013-10-21 15:55 -0400
    Re: What's wrong with Windows Command Prompt (was Re: Error Testing) Tim Chase <python.list@tim.thechases.com> - 2013-10-21 15:29 -0500

Page 2 of 2 — ← Prev page 1 [2]


#57121 — Re: What's wrong with Windows Command Prompt (was Re: Error Testing)

FromChris Angelico <rosuav@gmail.com>
Date2013-10-20 09:15 +1100
SubjectRe: What's wrong with Windows Command Prompt (was Re: Error Testing)
Message-ID<mailman.1268.1382220915.18130.python-list@python.org>
In reply to#57091
On Sun, Oct 20, 2013 at 7:35 AM, Terry Reedy <tjreedy@udel.edu> wrote:
> Idle can recall previous input two different ways, by cursor or key. One can
> use the mouse to select where to edit. CP requires use of arrow keys to move
> the cursor around. Idle recall input *statements*. CP recalls input *lines*.
> Previous multiline statements have to be recalled a line at a time. CP was
> not designed for true multiline commands (as opposed to long commands that
> wrap and display as multiple lines).

This issue applies also to Linux builds with readline. It's Idle's
primary boast, I think, closely followed by hover help for function
signatures.

ChrisA

[toc] | [prev] | [next] | [standalone]


#57123

FromChris Angelico <rosuav@gmail.com>
Date2013-10-20 09:20 +1100
Message-ID<mailman.1270.1382221243.18130.python-list@python.org>
In reply to#57091
On Sun, Oct 20, 2013 at 6:50 AM, Terry Reedy <tjreedy@udel.edu> wrote:
> On 10/19/2013 2:08 PM, David Robinow wrote:
>>
>> On Sat, Oct 19, 2013 at 9:01 AM, Chris Angelico <rosuav@gmail.com> wrote:
>>
>>> You can try all these out in the interactive interpreter (you probably
>>> have IDLE installed, which on Windows is rather nicer to work with
>>> than the default interactive mode).
>>
>>   IDLE is cross-platform.  Could you explain why you say "on Windows"?
>
>
> The command line console on *nix is apparently less obnoxious that the one
> on Windows. So for people who use an editor other than the Idle editor,
> there is less reason to use just the Idle shell.

Less obnoxious, more friendly, and way WAY more powerful. As I said in
the other thread, multi-line recall is its biggest lack, but for the
rest, it's quite usable. On Windows, not so much. (Mind you, I'm
accustomed to readline, so if you don't have it, you'll feel more
strongly about Idle.)

ChrisA

[toc] | [prev] | [next] | [standalone]


#57201 — Re: What's wrong with Windows Command Prompt (was Re: Error Testing)

FromDavid Robinow <drobinow@gmail.com>
Date2013-10-21 15:55 -0400
SubjectRe: What's wrong with Windows Command Prompt (was Re: Error Testing)
Message-ID<mailman.1317.1382385328.18130.python-list@python.org>
In reply to#57091
On Sat, Oct 19, 2013 at 4:35 PM, Terry Reedy <tjreedy@udel.edu> wrote:
> On 10/19/2013 2:31 PM, Tim Chase wrote:
>>
>> On 2013-10-19 14:08, David Robinow wrote:
>>>
>>> On Sat, Oct 19, 2013 at 9:01 AM, Chris Angelico wrote:
>>>>
>>>> You can try all these out in the interactive interpreter (you
>>>> probably have IDLE installed, which on Windows is rather nicer to
>>>> work with than the default interactive mode).
>>>
>>>
>>>   IDLE is cross-platform.  Could you explain why you say "on
>>> Windows"?
>> ...
>  [Description of idle  vs. Command Prompt]
 Not quite what I was trying to ask.
I'm well aware that Idle has features that the Python interpreter on
Windows doesn't.
Idle also has features that the unix variants doesn't.
I don't use my Ubuntu much so I'm somewhat ignorant, but I wasn't
aware that the interactive interpreter on Linux had features that the
Windows version didn't. I'm curious what those features might be.

[toc] | [prev] | [next] | [standalone]


#57204 — Re: What's wrong with Windows Command Prompt (was Re: Error Testing)

FromTim Chase <python.list@tim.thechases.com>
Date2013-10-21 15:29 -0500
SubjectRe: What's wrong with Windows Command Prompt (was Re: Error Testing)
Message-ID<mailman.1320.1382387285.18130.python-list@python.org>
In reply to#57091
On 2013-10-21 15:55, David Robinow wrote:
> I wasn't aware that the interactive interpreter on Linux had
> features that the Windows version didn't. I'm curious what those
> features might be.

It's mostly the benefits that come from being built with the readline
library, meaning you get

- command history (Win32 offers this, the rest not AFAIK)

- command-history searchability (control+R)

- the ability to pull down things from previous lines (alt+period in
  particular)

- the ability to comment out the currently typed command without
  executing it (alt+octothorpe)

- the ability to prefix text/commands with a count
  (alt+number_of_times followed by the character/command)

- the ability to insert matching filenames (alt+asterisk after typing
  path relative to the $CWD)

- clearing to the start/end of line (control+U/control+K)

- the ability to paste content (control+Y) previously-cut by ^U/^K

- the ability to transpose adjacent words (alt+T)

- the ability to jump forward/backward to a specified character
  (control+] and control+alt+] followed by the target char) like f/F
  in vi/vim

Those are just a subset of the power offered by readline when built
into Python's interpreter, none of which work (other than that first
one) on Win32's cmd.exe (or, I suppose command.com).

-tkc



[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.python


csiph-web