Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #72180 > unrolled thread
| Started by | Larry Martell <larry.martell@gmail.com> |
|---|---|
| First post | 2014-05-28 14:23 -0500 |
| Last post | 2014-05-31 09:28 -0800 |
| Articles | 20 on this page of 324 — 57 participants |
Back to article view | Back to comp.lang.python
Python 3 is killing Python Larry Martell <larry.martell@gmail.com> - 2014-05-28 14:23 -0500
Re: Python 3 is killing Python Johannes Bauer <dfnsonfsduifb@gmx.de> - 2014-05-28 21:39 +0200
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-05-28 22:41 +0300
Re: Python 3 is killing Python Paul Rubin <no.email@nospam.invalid> - 2014-05-28 12:49 -0700
Re: Python 3 is killing Python Larry Martell <larry.martell@gmail.com> - 2014-05-28 14:58 -0500
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-05-29 03:49 +0000
Re: Python 3 is killing Python Paul Rubin <no.email@nospam.invalid> - 2014-05-28 21:23 -0700
Re: Python 3 is killing Python Larry Martell <larry.martell@gmail.com> - 2014-05-29 06:38 -0500
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-05-29 06:15 +1000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-28 21:24 +0100
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-05-28 23:14 -0700
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-14 15:12 -0700
Re: Python 3 is killing Python mm0fmf <none@mailinator.com> - 2014-07-14 23:37 +0100
Re: Python 3 is killing Python MRAB <python@mrabarnett.plus.com> - 2014-07-14 23:47 +0100
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-14 18:00 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-15 11:18 +1000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-15 09:28 +1000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-14 18:54 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-15 12:11 +1000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-14 21:18 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-15 14:40 +1000
Re: Python 3 is killing Python Martin S <shieldfire@gmail.com> - 2014-07-15 06:31 +0200
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-15 05:41 +0000
Re: Python 3 is killing Python Tim Roberts <timr@probo.com> - 2014-07-16 20:18 -0700
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-16 22:15 -0700
Re: Python 3 is killing Python Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-07-17 17:36 +1200
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 15:45 +1000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 15:45 +1000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 08:05 +0100
Re: Python 3 is killing Python alister <alister.nospam.ware@ntlworld.com> - 2014-07-15 12:30 +0000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 00:59 +0100
Re: Python 3 is killing Python alister <alister.nospam.ware@ntlworld.com> - 2014-07-15 12:19 +0000
Re: Python 3 is killing Python MRAB <python@mrabarnett.plus.com> - 2014-07-15 15:50 +0100
Re: Python 3 is killing Python alister <alister.nospam.ware@ntlworld.com> - 2014-07-15 17:38 +0000
Re: Python 3 is killing Python Grant Edwards <invalid@invalid.invalid> - 2014-07-15 18:23 +0000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 16:35 +0100
Re: Python 3 is killing Python Ben Finney <ben@benfinney.id.au> - 2014-05-29 08:38 +1000
Re: Python 3 is killing Python Paul Rubin <no.email@nospam.invalid> - 2014-05-28 16:22 -0700
Re: Python 3 is killing Python beliavsky@aol.com - 2014-08-06 06:47 -0700
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-08-06 14:42 -0400
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-07 12:42 +1000
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-07 13:37 +1000
Re: Python 3 is killing Python Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-08-07 21:07 -0400
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-05-28 21:57 -0400
Re: Python 3 is killing Python Steve Hayes <hayesstw@telkomsa.net> - 2014-05-31 12:07 +0200
Re: Python 3 is killing Python Johannes Bauer <dfnsonfsduifb@gmx.de> - 2014-05-31 13:09 +0200
Re: Python 3 is killing Python Stefan Behnel <stefan_ml@behnel.de> - 2014-05-31 13:22 +0200
Re: Python 3 is killing Python Steve Hayes <hayesstw@telkomsa.net> - 2014-06-01 04:57 +0200
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-06-01 13:35 +1000
Re: Python 3 is killing Python Rustom Mody <rustompmody@gmail.com> - 2014-05-31 21:11 -0700
Re: Python 3 is killing Python Steve Hayes <hayesstw@telkomsa.net> - 2014-06-01 13:38 +0200
Re: Python 3 is killing Python Bob Martin <bob.martin@excite.com> - 2014-06-01 07:01 +0100
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-01 07:52 +0100
Re: Python 3 is killing Python Steve Hayes <hayesstw@telkomsa.net> - 2014-06-01 13:41 +0200
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-01 12:53 +0100
Re: Python 3 is killing Python alister <alister.nospam.ware@ntlworld.com> - 2014-06-01 17:21 +0000
Re: Python 3 is killing Python Bob Martin <bob.martin@excite.com> - 2014-06-02 07:14 +0100
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-05-31 12:30 +0000
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-05-31 08:48 -0700
Re: Python 3 is killing Python Ian Kelly <ian.g.kelly@gmail.com> - 2014-06-02 09:01 -0600
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-06-02 16:15 +0000
Re: Python 3 is killing Python Roy Smith <roy@panix.com> - 2014-06-02 12:21 -0400
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-06-03 02:30 +1000
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-06-02 16:52 +0000
Re: Python 3 is killing Python Johannes Bauer <dfnsonfsduifb@gmx.de> - 2014-06-02 19:16 +0200
Re: Python 3 is killing Python Ian Kelly <ian.g.kelly@gmail.com> - 2014-06-02 11:53 -0600
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-02 18:59 +0100
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-06-02 23:12 -0700
Re: Python 3 is killing Python Rustom Mody <rustompmody@gmail.com> - 2014-06-02 23:30 -0700
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-03 09:03 +0100
Re: Python 3 is killing Python Ned Batchelder <ned@nedbatchelder.com> - 2014-06-03 07:22 -0400
Re: Python 3 is killing Python Michael Torrie <torriem@gmail.com> - 2014-07-14 21:58 -0600
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-07-15 00:23 -0700
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 08:31 +0100
Re: Python 3 is killing Python Michael Torrie <torriem@gmail.com> - 2014-07-14 21:47 -0600
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-15 14:20 +1000
Re: Python 3 is killing Python Fabien <fabien.maussion@gmail.com> - 2014-07-15 14:17 +0200
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-15 23:00 +1000
Re: Python 3 is killing Python Kevin Walzer <kw@codebykevin.com> - 2014-07-15 09:57 -0400
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 00:31 +1000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-15 20:38 +0300
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-15 19:06 +0000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-15 23:01 +0300
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-16 03:51 +0000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 14:20 +1000
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-16 07:33 +0000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 08:52 +0300
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 16:26 +1000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 09:44 +0300
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 16:50 +1000
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-07-16 00:11 -0700
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-16 07:49 +0000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 18:44 +1000
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-16 11:35 +0000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 21:54 +1000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 13:46 +0300
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-16 12:10 +0000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 22:55 +1000
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-07-16 06:10 -0700
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 16:11 +0300
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-07-16 06:22 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 00:04 +1000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 17:39 +0300
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 01:23 +1000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 18:48 +0300
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 02:07 +1000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 19:20 +0300
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-17 02:51 +0000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 13:15 +1000
Re: Python 3 is killing Python MRAB <python@mrabarnett.plus.com> - 2014-07-17 12:27 +0100
Re: Python 3 is killing Python "Frank Millman" <frank@chagford.com> - 2014-07-17 07:18 +0200
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-17 07:49 +0000
Re: Python 3 is killing Python Rustom Mody <rustompmody@gmail.com> - 2014-07-30 14:31 -0700
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-16 17:02 -0400
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-16 18:47 -0400
Re: Python 3 is killing Python "Frank Millman" <frank@chagford.com> - 2014-07-16 16:27 +0200
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-16 15:41 -0700
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-17 00:00 +0100
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-16 18:16 -0700
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-17 03:14 +0000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-17 08:17 +0100
Re: Python 3 is killing Python alex23 <wuwei23@gmail.com> - 2014-07-18 12:49 +1000
Re: Python 3 is killing Python Dan Stromberg <drsalists@gmail.com> - 2014-07-17 20:34 -0700
Re: Python 3 is killing Python Grant Edwards <invalid@invalid.invalid> - 2014-07-18 14:17 +0000
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 13:20 +1000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-17 23:54 +0100
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-17 03:16 +0000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-16 21:47 -0700
Re: Python 3 is killing Python Fabien <fabien.maussion@gmail.com> - 2014-07-17 12:12 +0200
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 21:12 +1000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-17 11:15 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-18 04:27 +1000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-17 21:44 +0300
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-17 19:24 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-18 12:39 +1000
Re: Python 3 is killing Python Michael Torrie <torriem@gmail.com> - 2014-07-17 21:40 -0600
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-18 08:24 +0300
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 08:34 +0100
Re: Python 3 is killing Python Grant Edwards <invalid@invalid.invalid> - 2014-07-18 14:19 +0000
Re: Python 3 is killing Python Larry Martell <larry.martell@gmail.com> - 2014-07-18 08:35 -0600
Re: Python 3 is killing Python Torsten Bronger <bronger@physik.rwth-aachen.de> - 2014-07-18 17:25 +0200
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-18 19:45 -0400
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-17 20:06 +0100
Re: Python 3 is killing Python Emile van Sebille <emile@fenx.com> - 2014-07-17 12:22 -0700
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-17 21:37 +0100
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-17 17:30 -0400
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-17 20:13 -0400
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-18 18:38 +0000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 01:26 +0100
Re: Python 3 is killing Python alex23 <wuwei23@gmail.com> - 2014-07-18 12:54 +1000
Re: Python 3 is killing Python Andrew Berg <aberg010@my.hennepintech.edu> - 2014-07-17 19:45 -0500
Re: Python 3 is killing Python alex23 <wuwei23@gmail.com> - 2014-07-18 13:01 +1000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 16:45 +0100
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-18 12:15 +1000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-17 20:37 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-18 15:34 +1000
Re: Python 3 is killing Python Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-18 02:21 -0600
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-18 18:27 +1000
Re: Python 3 is killing Python MRAB <python@mrabarnett.plus.com> - 2014-07-18 16:46 +0100
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 16:49 +0100
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 16:50 +0100
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 17:22 +0100
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-18 21:27 -0400
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-18 21:21 -0400
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-19 09:29 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-20 02:41 +1000
Re: Python 3 is killing Python Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-19 12:00 -0600
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-19 13:39 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-20 09:13 +1000
Improving Idle (was Re: Python 3 ...) Terry Reedy <tjreedy@udel.edu> - 2014-07-19 16:45 -0400
Re: Improving Idle (was Re: Python 3 ...) Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-19 18:31 -0700
Re: Improving Idle (was Re: Python 3 ...) Chris Angelico <rosuav@gmail.com> - 2014-07-20 11:42 +1000
Re: Improving Idle (was Re: Python 3 ...) Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-20 12:40 +0100
Idle's Shell: prompts and indents (was ...) Idle users please read Terry Reedy <tjreedy@udel.edu> - 2014-07-20 17:52 -0400
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-20 18:22 -0700
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Chris Angelico <rosuav@gmail.com> - 2014-07-21 11:32 +1000
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Terry Reedy <tjreedy@udel.edu> - 2014-07-20 23:49 -0400
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Chris Angelico <rosuav@gmail.com> - 2014-07-21 10:55 +1000
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Terry Reedy <tjreedy@udel.edu> - 2014-07-20 23:28 -0400
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Chris Angelico <rosuav@gmail.com> - 2014-07-21 13:34 +1000
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Terry Reedy <tjreedy@udel.edu> - 2014-07-21 05:00 -0400
Re: Idle's Shell: prompts and indents (was ...) Idle users please read wxjmfauth@gmail.com - 2014-07-21 13:00 -0700
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Chris Angelico <rosuav@gmail.com> - 2014-07-21 20:56 +1000
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Terry Reedy <tjreedy@udel.edu> - 2014-07-21 14:30 -0400
Re: Idle's Shell: prompts and indents (was ...) Idle users please read Chris Angelico <rosuav@gmail.com> - 2014-07-22 04:35 +1000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-19 15:50 -0700
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-19 19:23 -0400
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-20 09:10 +1000
Re: Improving Idle (was Re: Python 3 ...) Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-21 02:54 +0100
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 08:24 +0100
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-18 18:20 +0000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-18 19:31 +0100
Re: Python 3 is killing Python MRAB <python@mrabarnett.plus.com> - 2014-07-18 20:44 +0100
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-18 14:37 -0700
Re: Python 3 is killing Python Ned Batchelder <ned@nedbatchelder.com> - 2014-07-18 18:09 -0400
Python and IDEs [was Re: Python 3 is killing Python] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-19 07:28 +0000
Re: Python and IDEs [was Re: Python 3 is killing Python] "C.D. Reimer" <chris@cdreimer.com> - 2014-07-19 11:08 -0700
Re: Python and IDEs [was Re: Python 3 is killing Python] Terry Reedy <tjreedy@udel.edu> - 2014-07-19 14:31 -0400
Re: Python and IDEs [was Re: Python 3 is killing Python] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-20 01:23 +0000
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-07-20 11:39 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] "C.D. Reimer" <chris@cdreimer.com> - 2014-07-19 18:53 -0700
Re: Python and IDEs [was Re: Python 3 is killing Python] CHIN Dihedral <dihedral88888@gmail.com> - 2014-07-21 08:37 -0700
Re: Python and IDEs [was Re: Python 3 is killing Python] Tim Delaney <timothy.c.delaney@gmail.com> - 2014-07-20 14:18 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Tim Delaney <timothy.c.delaney@gmail.com> - 2014-07-20 07:50 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-07-20 09:19 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Tim Delaney <timothy.c.delaney@gmail.com> - 2014-07-20 10:41 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] "C.D. Reimer" <chris@cdreimer.com> - 2014-07-19 18:24 -0700
Re: Python and IDEs [was Re: Python 3 is killing Python] TP <wingusr@gmail.com> - 2014-07-19 19:03 -0700
Re: Python and IDEs [was Re: Python 3 is killing Python] "C.D. Reimer" <chris@cdreimer.com> - 2014-07-19 20:10 -0700
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-01 13:10 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-01 21:22 +1000
Re: Python and IDEs Marko Rauhamaa <marko@pacujo.net> - 2014-08-01 15:19 +0300
Re: Python and IDEs Chris Angelico <rosuav@gmail.com> - 2014-08-01 22:30 +1000
Re: Python and IDEs Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-01 23:10 +1000
Re: Python and IDEs Chris Angelico <rosuav@gmail.com> - 2014-08-01 23:30 +1000
Re: Python and IDEs Marko Rauhamaa <marko@pacujo.net> - 2014-08-01 18:13 +0300
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-06 14:38 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-06 22:51 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-11 11:08 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Nicholas Cole <nicholas.cole@gmail.com> - 2014-08-01 15:28 +0100
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-06 14:47 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-07 13:32 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-11 11:08 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] alister <alister.nospam.ware@ntlworld.com> - 2014-08-11 09:37 +0000
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-11 20:20 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-11 14:45 +0100
Re: Python and IDEs [was Re: Python 3 is killing Python] Grant Edwards <invalid@invalid.invalid> - 2014-08-11 18:42 +0000
Re: Python and IDEs [was Re: Python 3 is killing Python] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-12 10:11 +1000
Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python]) Tim Chase <python.list@tim.thechases.com> - 2014-08-11 19:27 -0500
Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python]) Steven D'Aprano <steve@pearwood.info> - 2014-08-12 02:07 +0000
Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python]) Chris Angelico <rosuav@gmail.com> - 2014-08-12 12:13 +1000
Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python]) Tim Chase <python.list@tim.thechases.com> - 2014-08-11 21:23 -0500
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-13 12:42 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-13 23:35 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-13 16:51 +0100
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-02 00:39 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-02 11:14 +1200
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-02 09:50 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Olaf Hering <olaf@aepfle.de> - 2014-08-02 09:10 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-02 23:38 +1200
Re: Python and IDEs [was Re: Python 3 is killing Python] Dietmar Schwertberger <maillist@schwertberger.de> - 2014-08-01 19:16 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-06 14:47 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Grant Edwards <invalid@invalid.invalid> - 2014-08-11 18:39 +0000
Re: Python and IDEs [was Re: Python 3 is killing Python] Wolfgang Keller <feliphil@gmx.net> - 2014-08-13 13:46 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Michael Torrie <torriem@gmail.com> - 2014-08-01 14:22 -0600
Re: Python and IDEs [was Re: Python 3 is killing Python] MRAB <python@mrabarnett.plus.com> - 2014-08-01 22:09 +0100
Re: Python and IDEs [was Re: Python 3 is killing Python] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-02 12:00 +1200
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-02 10:20 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-02 23:33 +1200
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-02 23:01 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-03 12:01 +1200
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-03 11:12 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] MRAB <python@mrabarnett.plus.com> - 2014-08-02 14:55 +0100
Re: Python and IDEs [was Re: Python 3 is killing Python] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-03 12:04 +1200
Re: Python and IDEs [was Re: Python 3 is killing Python] Dietmar Schwertberger <maillist@schwertberger.de> - 2014-08-03 09:46 +0200
Re: Python and IDEs [was Re: Python 3 is killing Python] Roy Smith <roy@panix.com> - 2014-08-02 10:27 -0400
Re: Python and IDEs [was Re: Python 3 is killing Python] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-03 12:20 +1200
Re: Python and IDEs [was Re: Python 3 is killing Python] Chris Angelico <rosuav@gmail.com> - 2014-08-02 09:48 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Duncan Booth <duncan.booth@invalid.invalid> - 2014-08-05 13:29 +0000
Re: Python and IDEs [was Re: Python 3 is killing Python] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-06 02:50 +1000
Re: Python and IDEs [was Re: Python 3 is killing Python] Duncan Booth <duncan.booth@invalid.invalid> - 2014-08-05 19:25 +0000
Re: Python and IDEs [was Re: Python 3 is killing Python] TP <wingusr@gmail.com> - 2014-08-05 14:28 -0700
Re: Python 3 is killing Python Terry Reedy <tjreedy@udel.edu> - 2014-07-18 19:26 -0400
Re: Python 3 is killing Python Kevin Walzer <kw@codebykevin.com> - 2014-08-03 21:21 -0400
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 01:18 +1000
Re: Python 3 is killing Python Javier <nospam@nospam.com> - 2014-07-16 17:33 +0000
Re: Python 3 is killing Python Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-16 11:50 -0600
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-17 03:33 +0000
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-17 04:25 +0000
Re: Python 3 is killing Python "Neil D. Cerutti" <neilc@norwich.edu> - 2014-07-16 11:48 -0400
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-16 18:34 +0100
Re: Python 3 is killing Python "Frank Millman" <frank@chagford.com> - 2014-07-17 08:31 +0200
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 16:41 +1000
Re: Python 3 is killing Python "Frank Millman" <frank@chagford.com> - 2014-07-17 09:09 +0200
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 17:59 +1000
Re: Python 3 is killing Python Glenn Linderman <v+python@g.nevcal.com> - 2014-08-01 23:18 -0700
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 21:24 +0100
Re: Python 3 is killing Python Devin Jeanpierre <jeanpierreda@gmail.com> - 2014-07-15 13:47 -0700
Re: Python 3 is killing Python Abhiram R <abhi.darkness@gmail.com> - 2014-07-16 03:07 +0530
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-16 02:08 +0000
Re: Python 3 is killing Python Abhiram R <abhi.darkness@gmail.com> - 2014-07-16 03:05 +0530
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 22:49 +0100
Re: Python 3 is killing Python Abhiram R <abhi.darkness@gmail.com> - 2014-07-16 03:43 +0530
Re: Python 3 is killing Python Kevin Walzer <kw@codebykevin.com> - 2014-07-15 18:30 -0400
Re: Python 3 is killing Python Abhiram R <abhi.darkness@gmail.com> - 2014-07-16 04:10 +0530
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-15 16:53 -0700
Re: Python 3 is killing Python MRAB <python@mrabarnett.plus.com> - 2014-07-16 02:57 +0100
Re: Python 3 is killing Python Tim Roberts <timr@probo.com> - 2014-07-16 20:20 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-17 13:38 +1000
Re: Python 3 is killing Python Abhiram R <abhi.darkness@gmail.com> - 2014-07-16 09:07 +0530
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-16 09:18 +0100
Re: Python 3 is killing Python Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-07-16 12:20 +0200
Re: Python 3 is killing Python Ben Finney <ben@benfinney.id.au> - 2014-07-17 14:17 +1000
Re: Python 3 is killing Python Joshua Landau <joshua@landau.ws> - 2014-07-16 00:45 +0100
Interleaved posting style for text discussion forums (was: Python 3 is killing Python) Ben Finney <ben@benfinney.id.au> - 2014-07-17 14:02 +1000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 23:38 +0100
Re: Python 3 is killing Python Kevin Walzer <kw@codebykevin.com> - 2014-07-15 20:43 -0400
Re: Python 3 is killing Python Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-07-15 23:05 -0400
Re: Python 3 is killing Python Grant Edwards <invalid@invalid.invalid> - 2014-07-16 13:59 +0000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-15 11:01 -0700
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-15 21:08 +0300
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-15 18:57 +0000
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-07-15 22:49 +0300
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-15 18:53 +0000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-15 13:20 -0700
Re: Python 3 is killing Python Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-15 14:46 -0600
Re: Python 3 is killing Python Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-15 12:53 -0600
Re: Python 3 is killing Python Anders Wegge Keller <wegge@wegge.dk> - 2014-07-15 17:02 +0200
Re: Python 3 is killing Python Grant Edwards <invalid@invalid.invalid> - 2014-07-15 15:43 +0000
Re: Python 3 is killing Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-15 16:44 +0100
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-16 01:48 +1000
Re: Python 3 is killing Python alex23 <wuwei23@gmail.com> - 2014-07-17 15:48 +1000
Re: Python 3 is killing Python Steven D'Aprano <steve@pearwood.info> - 2014-07-17 07:03 +0000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-17 10:36 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-18 03:52 +1000
Re: Python 3 is killing Python Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-17 11:38 -0700
Re: Python 3 is killing Python Chris Angelico <rosuav@gmail.com> - 2014-07-18 04:48 +1000
Re: Python 3 is killing Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-18 18:01 +0000
Re: Python 3 is killing Python wxjmfauth@gmail.com - 2014-07-15 06:33 -0700
Re: Python 3 is killing Python Steve Hayes <hayesstw@telkomsa.net> - 2014-06-01 05:00 +0200
Re: Python 3 is killing Python Marko Rauhamaa <marko@pacujo.net> - 2014-05-31 15:44 +0300
Re: Python 3 is killing Python Steve Hayes <hayesstw@telkomsa.net> - 2014-06-01 05:05 +0200
Re: Python 3 is killing Python pyotr filipivich <phamp@mindspring.com> - 2014-07-12 10:50 -0700
Re: Python 3 is killing Python Deb Wyatt <codemonkey@inbox.com> - 2014-05-31 09:28 -0800
Page 8 of 17 — ← Prev page 1 … 6 7 [8] 9 10 … 17 Next page →
| From | Torsten Bronger <bronger@physik.rwth-aachen.de> |
|---|---|
| Date | 2014-07-18 17:25 +0200 |
| Message-ID | <87tx6eofja.fsf@physik.rwth-aachen.de> |
| In reply to | #74751 |
Hallöchen!
Larry Martell writes:
> On Fri, Jul 18, 2014 at 8:19 AM, Grant Edwards <invalid@invalid.invalid> wrote:
>
>> But, I do know that a decent, civilized person just doesn't make
>> insulting comments like that about somebody else's work even if
>> it is true (which I very much doubt).
>
> Now, _that's_ funny. This is the internet. If you can't stand the
> heat get out of the kitchen.
Now, _that's_ funny. This is the internet. If you can't stand people
who can't stand the heat get out of the kitchen.
Tschö,
Torsten.
--
Torsten Bronger Jabber ID: torsten.bronger@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
[toc] | [prev] | [next] | [standalone]
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2014-07-18 19:45 -0400 |
| Message-ID | <mailman.12025.1405727167.18130.python-list@python.org> |
| In reply to | #74712 |
On 7/17/2014 10:39 PM, Chris Angelico wrote: > IDLE (or Idle; Terry > seems to spell it the latter way, I'm not sure what's the official > recommendation now), You found me out ;-). FORTRAN is now Fortran, and I hate typing IDLE, and that spelling somehow strikes me as pretentious, so I decided to un-officially promote Idle by typing it this way. -- Terry Jan Reedy
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2014-07-17 20:06 +0100 |
| Message-ID | <mailman.11953.1405624031.18130.python-list@python.org> |
| In reply to | #74663 |
On 17/07/2014 19:15, Rick Johnson wrote: > On Thursday, July 17, 2014 5:12:23 AM UTC-5, Fabien wrote: > > Sadly, all of my calls to improve IDLE have been meet with > rebukes about me "whining". The "powers that be" would wise > to *UTILIZE* and *ENCOURAGE* my participation instead of > *IGNORING* valuable talent and *IMPEDING* the expansion of > this "private boys club". > Terry Reedy and Co have been pouring improvements into IDLE via the bug tracker for months if not years. How many times have you logged on there to help out? The background that allows this to happen http://legacy.python.org/dev/peps/pep-0434/. How strongly this contrasts with '*IGNORING* valuable talent and *IMPEDING* the expansion of this "private boys club"'. -- 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
[toc] | [prev] | [next] | [standalone]
| From | Emile van Sebille <emile@fenx.com> |
|---|---|
| Date | 2014-07-17 12:22 -0700 |
| Message-ID | <mailman.11954.1405624993.18130.python-list@python.org> |
| In reply to | #74663 |
On 7/17/2014 11:15 AM, Rick Johnson wrote: > Sadly, all of my calls to improve IDLE have been meet with > rebukes about me "whining". The "powers that be" would wise > to *UTILIZE* and *ENCOURAGE* my participation instead of > *IGNORING* valuable talent and *IMPEDING* the expansion of > this "private boys club". I imagine those that would be in a position to improve idle don't see the point of it. IMO, idle was never intended as a production development editor but more as an extensive example of gui programming with python. Yes, you _can_ use it to edit, and there are nice python hooks, but I doubt that anyone with the skills to enhance idle actually uses idle. You-can-also-program-using-notepad-eeew-ly y'rs, Emile
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2014-07-17 21:37 +0100 |
| Message-ID | <mailman.11961.1405629466.18130.python-list@python.org> |
| In reply to | #74663 |
On 17/07/2014 20:22, Emile van Sebille wrote: > On 7/17/2014 11:15 AM, Rick Johnson wrote: > >> Sadly, all of my calls to improve IDLE have been meet with >> rebukes about me "whining". The "powers that be" would wise >> to *UTILIZE* and *ENCOURAGE* my participation instead of >> *IGNORING* valuable talent and *IMPEDING* the expansion of >> this "private boys club". > > I imagine those that would be in a position to improve idle don't see > the point of it. IMO, idle was never intended as a production > development editor but more as an extensive example of gui programming > with python. Yes, you _can_ use it to edit, and there are nice python > hooks, but I doubt that anyone with the skills to enhance idle actually > uses idle. > > You-can-also-program-using-notepad-eeew-ly y'rs, > > Emile > Some of the top core developers teach classes using IDLE as it's the only tool guaranteed to be available on all the major platforms. You might also like to view this https://www.youtube.com/watch?v=d1a4Jbjc-vU -- 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
[toc] | [prev] | [next] | [standalone]
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2014-07-17 17:30 -0400 |
| Message-ID | <mailman.11963.1405632692.18130.python-list@python.org> |
| In reply to | #74663 |
On 7/17/2014 3:22 PM, Emile van Sebille wrote: > I imagine those that would be in a position to improve idle don't see > the point of it. IMO, idle was never intended as a production > development editor but more as an extensive example of gui programming > with python. Yes, you _can_ use it to edit, and there are nice python > hooks, but I doubt that anyone with the skills to enhance idle actually > uses idle. That is something of a problem as people 'graduate' to multi-language environments. However, while I have programmed in about 20 languages during my lifetime, I have now 'contracted' to using only Python (except for the occasional .bat file). So I use Idle to work on both my own stuff and on fixing Idle. When I notice an issue while working on an issue, I file a new issue. -- Terry Jan Reedy
[toc] | [prev] | [next] | [standalone]
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2014-07-17 20:13 -0400 |
| Message-ID | <mailman.11970.1405642467.18130.python-list@python.org> |
| In reply to | #74663 |
On 7/17/2014 2:15 PM, Rick Johnson wrote: a partial disinformation rant again Idle that repeats things said before, more than once. In general, your rants seem to serve the social purpose of providing cover to other people to join in loose, off-topic discussions. In this one, you align yourself with the 'private boys club' idle haters you profess to disdain. Some facts. Idlelib has about 60 modules. The tracker has, as I write, 133 open issues (behavior and enhancements, with the boundary sometimes fuzzy) marked Component: Idle. That is about two issues per module. It is definitely less than 1 bug per 100 lines. There is only 1 bug, Windows-specific, that routinely gets in my way. The stdlib has, I believe, less than 1000 modules. There are right now 4545 open issues, or at least 4, maybe more, per module. Anyone who calls Idle (or anything else) 'buggy' and 'embarassing' should do some research and say 'compared to what' and 'by what standard'. Last January, I discovered that tokenize.untokenize had about 5 bugs in about 25 lines of code. The new mode was hardly usable. I think *that* could be called 'embarassing' -- compared to the rest of the stdlib and by the standard of being basically usable. I fixed all but 1 of the implementation bugs. More facts. Since 2.7 was released in July 2010, there have been 94 issues with improvements recorded in idlelib/news.txt (extracted from the 2.7 news/changelog). (Some issues have multiple patches, and some patches no recorded issue, but we can stick with the recorded issue count.) Has the patch rate gone down or up? Over half (46) of the issue patches are recorded in the last 15 months out of 48, less than a third, after the release of 2.7.5 on 2013 April 4. The reason for the uptick is PEP 434, which ended the blockage of Idle patches by useless debates over 'behavior' versus 'enhancement' and backport or not'. It also ended (most of) the Idle hate rants on pydev. > Sadly, all of my calls to improve IDLE have been meet with > rebukes about me "whining". Each of the 133 issues on the tracker is a specific, usually actionable, 'call' to improve Idle. They are gradually being attended to. Generic 'calls for improvement' on this list are useless. > The "powers that be" When it comes to Idle, that means me as much as anyone. > would wise to *UTILIZE* and *ENCOURAGE* my participation <blah blah ...> Still more facts ;-). About three (four?) years ago, you posted a similar rant. Being wise, I encouraged your participation and utilized the patch you anonymously posted on the tracker (to maintain your Ranting Rick pose) in one of my first commits. I invite you to resume your participation, either anonymously or openly. As before, you can email me privately to discuss what would best suite you and also be helpful. I will mention that one barrier to improving Idle code, beyond making small local fixes, is the need for automated tests before refactoring. I started a unittest suite in May 2013 with the help of GSOC (Google Summer of Code) students. In May 2014, this year's student and I collected together and improved the human-run tests. -- Terry Jan Reedy
[toc] | [prev] | [next] | [standalone]
| From | Steven D'Aprano <steve+comp.lang.python@pearwood.info> |
|---|---|
| Date | 2014-07-18 18:38 +0000 |
| Message-ID | <53c9699c$0$9505$c3e8da3$5496439d@news.astraweb.com> |
| In reply to | #74702 |
On Thu, 17 Jul 2014 20:13:44 -0400, Terry Reedy wrote: > On 7/17/2014 2:15 PM, Rick Johnson wrote: a partial disinformation rant > again Idle that repeats things said before, more than once. [...] Thanks for the detailed explanation Terry, and especially thanks for the good work you have done on IDLE. I'll admit I don't use it, I dislike the UI, but given all the solid work you and the GSOC students have put into it, perhaps I ought to check it out again soon. > Still more facts ;-). About three (four?) years ago, you posted a > similar rant. Being wise, I encouraged your participation and utilized > the patch you anonymously posted on the tracker (to maintain your > Ranting Rick pose) in one of my first commits. Well well, I must admit I am shocked to learn that Rick has actually written some Python code. -- Steven
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2014-07-18 01:26 +0100 |
| Message-ID | <mailman.11972.1405643210.18130.python-list@python.org> |
| In reply to | #74663 |
On 18/07/2014 01:13, Terry Reedy wrote: > On 7/17/2014 2:15 PM, Rick Johnson wrote: > a partial disinformation rant again Idle > that repeats things said before, more than once. > > Still more facts ;-). About three (four?) years ago, you posted a > similar rant. Being wise, I encouraged your participation and utilized > the patch you anonymously posted on the tracker (to maintain your > Ranting Rick pose) in one of my first commits. I invite you to resume > your participation, either anonymously or openly. As before, you can > email me privately to discuss what would best suite you and also be > helpful. > I'm looking forward to see the massive number of fixes that come from rr, assuming of course that he signs the CLA to make this possible. Or has he already done so? -- 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
[toc] | [prev] | [next] | [standalone]
| From | alex23 <wuwei23@gmail.com> |
|---|---|
| Date | 2014-07-18 12:54 +1000 |
| Message-ID | <lqa28k$nkp$2@dont-email.me> |
| In reply to | #74704 |
On 18/07/2014 10:26 AM, Mark Lawrence wrote: > I'm looking forward to see the massive number of fixes that come from > rr I'm still waiting for RickPython, the One True Python. Remember when he used to rant as if he was actually working on it and not just pissing in the wind?
[toc] | [prev] | [next] | [standalone]
| From | Andrew Berg <aberg010@my.hennepintech.edu> |
|---|---|
| Date | 2014-07-17 19:45 -0500 |
| Message-ID | <mailman.11973.1405644337.18130.python-list@python.org> |
| In reply to | #74663 |
On 2014.07.17 19:26, Mark Lawrence wrote: > I'm looking forward to see the massive number of fixes that come from > rr, assuming of course that he signs the CLA to make this possible. Or > has he already done so? > Maybe he's too busy working on RickPy 4000 (or whatever it was called).
[toc] | [prev] | [next] | [standalone]
| From | alex23 <wuwei23@gmail.com> |
|---|---|
| Date | 2014-07-18 13:01 +1000 |
| Message-ID | <lqa2lp$nkp$3@dont-email.me> |
| In reply to | #74705 |
On 18/07/2014 10:45 AM, Andrew Berg wrote: > Maybe he's too busy working on RickPy 4000 (or whatever it was called). I believe the new working name is PypeDream.
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2014-07-18 16:45 +0100 |
| Message-ID | <mailman.12003.1405698380.18130.python-list@python.org> |
| In reply to | #74717 |
On 18/07/2014 04:01, alex23 wrote: > On 18/07/2014 10:45 AM, Andrew Berg wrote: >> Maybe he's too busy working on RickPy 4000 (or whatever it was called). > > I believe the new working name is PypeDream. > For me a very good day just got better with that one, thanks :) -- 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
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-07-18 12:15 +1000 |
| Message-ID | <mailman.11976.1405649724.18130.python-list@python.org> |
| In reply to | #74663 |
On Fri, Jul 18, 2014 at 7:30 AM, Terry Reedy <tjreedy@udel.edu> wrote: > That is something of a problem as people 'graduate' to multi-language > environments. However, while I have programmed in about 20 languages during > my lifetime, I have now 'contracted' to using only Python (except for the > occasional .bat file). So I use Idle to work on both my own stuff and on > fixing Idle. When I notice an issue while working on an issue, I file a new > issue. Glad to hear it. Best way to make sure Idle stays developed is for its core developers to actively use it. For myself, though, I completely do not use the editor half of it; but it's spectacularly useful (with limitations) as my primary interactive interpreter. That's partly because, on Windows, the command-line interpreter absolutely *sucks* (because most of its UI comes from cmd.exe - my view might be different if I had a different shell, but there's no point because Idle just blows it away), and partly because command recall/editing works on entire syntactic units rather than on lines. In fact, if I were to name *one single feature* that made Idle useful rather than a mere toy, it would have to be the ability to recall an entire function/class definition from command history for further editing. That is hugely helpful to me. It's what makes Python actually 100% usable in interactive mode - go right ahead, define functions and classes just as you would in a file! (Okay, you have to watch out about blank lines. Not usually an issue, but you'll possibly notice that I seldom have any internal blanks when I post a class definition on-list - it's because I usually write them in Idle.) 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. ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Rick Johnson <rantingrickjohnson@gmail.com> |
|---|---|
| Date | 2014-07-17 20:37 -0700 |
| Message-ID | <bd84e8d5-5e30-492d-92be-1f061e8d11fe@googlegroups.com> |
| In reply to | #74711 |
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!!!
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-07-18 15:34 +1000 |
| Message-ID | <mailman.11984.1405661675.18130.python-list@python.org> |
| In reply to | #74721 |
On Fri, Jul 18, 2014 at 1:37 PM, Rick Johnson <rantingrickjohnson@gmail.com> wrote: > I'm also just "gushing with exuberance" when i open a new > block and i get *EIGHT SPACE INDENTION*! Actually, you don't. And it wouldn't be a bug if you did. ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| Date | 2014-07-18 02:21 -0600 |
| Message-ID | <mailman.11989.1405671722.18130.python-list@python.org> |
| In reply to | #74721 |
On Thu, Jul 17, 2014 at 9:37 PM, Rick Johnson <rantingrickjohnson@gmail.com> 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 just tried to reproduce this using IDLE 3.4 on Windows and was not able to. > I'm also just "gushing with exuberance" when i open a new > block and i get *EIGHT SPACE INDENTION*! In the file editor when I press Tab I get four spaces as I would expect, using the default configuration. In the interactive interpreter I get an actual tab character again as I would expect. That's probably as it should be since I wouldn't want to not be able to type a tab character there.
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-07-18 18:27 +1000 |
| Message-ID | <mailman.11991.1405672032.18130.python-list@python.org> |
| In reply to | #74721 |
On Fri, Jul 18, 2014 at 6:21 PM, Ian Kelly <ian.g.kelly@gmail.com> wrote: >> 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 just tried to reproduce this using IDLE 3.4 on Windows and was not able to. Actually, now you mention it, I do recall experiencing a bug like this in previous versions. It's not the case in either my 2.7 (point something, but I don't remember what) nor 3.4, so I'm guessing it's been fixed. ChrisA
[toc] | [prev] | [next] | [standalone]
| From | MRAB <python@mrabarnett.plus.com> |
|---|---|
| Date | 2014-07-18 16:46 +0100 |
| Message-ID | <mailman.12004.1405698402.18130.python-list@python.org> |
| In reply to | #74721 |
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?
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2014-07-18 16:49 +0100 |
| Message-ID | <mailman.12005.1405698613.18130.python-list@python.org> |
| In reply to | #74721 |
On 18/07/2014 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!!! > This is patently wrong, IDLE is constantly being improved. I also don't recall ever seeing a bug report from yourself about IDLE. Your gretest strength seems to be complaining, your biggest weakness doing anything about whatever it is that you're complaining about. -- 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
[toc] | [prev] | [next] | [standalone]
Page 8 of 17 — ← Prev page 1 … 6 7 [8] 9 10 … 17 Next page →
Back to top | Article view | comp.lang.python
csiph-web