[Python-Dev] IDLE in the stdlib (original) (raw)
Terry Reedy tjreedy at udel.edu
Thu Mar 21 01:30:23 CET 2013
- Previous message: [Python-Dev] IDLE in the stdlib
- Next message: [Python-Dev] IDLE in the stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/20/2013 3:59 PM, Brian Curtin wrote:
On Wed, Mar 20, 2013 at 2:51 PM, Xavier Morel <python-dev at masklinn.net> wrote:
That would be a blow to educators, but also Windows users: while the CLI works very nicely in unices, that's not the case with the win32 console which is as best as I can describe it a complete turd, making IDLE a very nice proposition there (I never use IDLE on Linux or OSX, but do all the time in Windows). Can you explain this a bit more? I've been using the CLI python.exe on Windows, Mac, and Linux for years and I don't know what you're talking about.
I gave examples in my response to the original post: ^C,^V do not work (but do in IDLE); the output buffer cannot even hold the entire 'help(str)' response (IDLE can, and much more) ; by default, print() cannot even print all latin-1 chars, let alone the BMP (IDLE will at least print a box for the entire BMP); CP is frozen in time 30 years ago, while IDLE is being maintained and modernized.
-- Terry Jan Reedy
- Previous message: [Python-Dev] IDLE in the stdlib
- Next message: [Python-Dev] IDLE in the stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]