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 3 of 17 — ← Prev page 1 2 [3] 4 5 … 17 Next page →
| From | Steven D'Aprano <steve+comp.lang.python@pearwood.info> |
|---|---|
| Date | 2014-08-07 12:42 +1000 |
| Message-ID | <53e2e78f$0$30002$c3e8da3$5496439d@news.astraweb.com> |
| In reply to | #75809 |
Terry Reedy wrote: > On 8/6/2014 9:47 AM, beliavsky@aol.com.dmarc.invalid wrote: > >> Fortran compiler vendors such as Intel, IBM, Oracle/SUN and open > > *Vendors* sell compilers for money, which they can then use to *pay* > people to do unfun stuff that volunteers don't want and should not have > to do. Red Hat does this, and will offer support for 2.7 until 2023. But even Red Hat doesn't offer to support software forever -- Python 2.3 has just reached end of life with paid Red Hat support earlier this year. Anyone still using 2.3 now has two choices, keep using it without support, or upgrade. The same will apply to 2.7 users. It's not like their computer will suddenly stop running 2.7. Come 2020 when Python 2.7 stops receiving free support from the core developers, there's a business opportunity for the 2.7-naysayers. Red Hat support is Red Hat Enterprise Linux only. There may be paid support from companies like ActiveState, but that's likely to be Windows only (I could be wrong about that). So there's the opportunity: in 2020, those naysayers who are convinced that Python 3 is a mistake can offer paid support on whatever platforms they like. > Actually, I am beginning to think that 2.7 should be split off for 3.x > development and charged for. Python is open source. Anyone can fork it, and release 2.8, 2.9, 2.10, as many versions they like. The only thing they can't do is call it "Python 2.8" without agreement from the PSF, which they won't get. But they won't fork it, for two reasons: Complaining is cheap, actually maintaining a programming language is hard work. And deep down they know that a fork will be just a waste of time. This is not like the fork of the X-11 windowing system a few years back, for all the complaints and whinging about Python 3 even the nay-sayers know that the world will remain full behind Guido, the core developers and the PSF, who are all committed to Python 3. Let me be frank here: the core developers are committed to making the process of migrating from 2 to 3 as easy as possible without compromising Python 3 in any serious manner. E.g. minor cosmetic warts, like the re-introduction of u"" syntax just for backwards compatibility reasons, may be allowed, reversing design decisions like strings being Unicode rather than bytes will not be. But ultimately, people will need to make a choice: - spend the time and effort and money to migrate from Python 2 to 3; - spend an order of magnitude more time and effort and money to re-write their applications in another language; - pay somebody to support Python 2.7 for as long as needed; - or do without bug fixes and security updates. If you want bug fixes, security updates AND feature enhancements, for free, you have have to migrate to Python 3 (or another language). If you're unhappy with that, write to Oprah, I'm sure she'll listen. -- Steven
[toc] | [prev] | [next] | [standalone]
| From | Steven D'Aprano <steve+comp.lang.python@pearwood.info> |
|---|---|
| Date | 2014-08-07 13:37 +1000 |
| Message-ID | <53e2f47a$0$6512$c3e8da3$5496439d@news.astraweb.com> |
| In reply to | #75802 |
beliavsky@aol.com wrote: > Fortran compiler vendors such as Intel, IBM, Oracle/SUN and open source > projects such as gfortran are updating their compilers to the Fortran 2003 > and 2008 standards while also keeping the ability to compile all the old > Fortran code. FORTRAN 77 programmers and programs will not be forced to > move to modern Fortran, How about FORTRAN IV and FORTRAN 66 users? Where's their support? Why aren't they moaning and gnashing their teeth that they're so cruelly and unreasonably forced to upgrade? > but I'm not sure that Python 2.x users can be as > confident that Python 2.x will be supported on future operating systems. Oh well, life wasn't meant to be easy. Fortunately they can run it under Windows 98 or Centos 3.5 in a virtual machine. -- Steven
[toc] | [prev] | [next] | [standalone]
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Date | 2014-08-07 21:07 -0400 |
| Message-ID | <mailman.12731.1407460120.18130.python-list@python.org> |
| In reply to | #75828 |
On Thu, 07 Aug 2014 13:37:29 +1000, Steven D'Aprano
<steve+comp.lang.python@pearwood.info> declaimed the following:
>beliavsky@aol.com wrote:
>
>> Fortran compiler vendors such as Intel, IBM, Oracle/SUN and open source
>> projects such as gfortran are updating their compilers to the Fortran 2003
>> and 2008 standards while also keeping the ability to compile all the old
>> Fortran code. FORTRAN 77 programmers and programs will not be forced to
>> move to modern Fortran,
>
>How about FORTRAN IV and FORTRAN 66 users? Where's their support? Why aren't
>they moaning and gnashing their teeth that they're so cruelly and
>unreasonably forced to upgrade?
>
Most likely, the formal standard document for Fortran still mandates
F77 compatibility -- yet most likely also lists those F77 features which
are deprecated/obsolete and may go away in the next standard. Just as F77
standard listed F-IV features that would be going away in the future.
Also, being a fully compiled/static language, the compiler can probably
spend the needed time to determine the dialect being used for some
constructs. Python's run-time dynamics may preclude doing that.
Third -- said compatibility may still require using a compile-time flag
to indicate dialect for some features.
Heck, at one time the "FORTRAN standard" actually defined two levels of
the language, and the subset level could not compile stuff that was legal
in the full language level. Things like computed arguments in a subprogram
call:
call xyz(i-1, i, i+1)
could be valid or invalid depending upon which level of the single standard
the compiler followed. I once was involved in an effort that ported an
application in "full" FORTRAN to a machine with the subset level. You
wouldn't believe the number of
inxs, inks, jinx, jynx, jinks, linx, lynx, lyncs etc. junk variables had to
be created:
jinx = i-1
lynx = i+1
call xyz(jinx, i, lynx)
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
[toc] | [prev] | [next] | [standalone]
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2014-05-28 21:57 -0400 |
| Message-ID | <mailman.10432.1401328660.18130.python-list@python.org> |
| In reply to | #72184 |
On 5/28/2014 3:49 PM, Paul Rubin wrote: > Larry Martell <larry.martell@gmail.com> writes: >> Somthing I came across in my travels through the ether: >> [1]https://medium.com/@deliciousrobots/5d2ad703365d/ > > "Python 3 can revive Python" https://medium.com/p/2a7af4788b10 This makes the same false claim "It’s not like anyone is using Python 3 anyway, (so go ahead and bread existing Py3 code". At least some of the 20+ million windows downloads must be in use. > long HN comment thread: https://news.ycombinator.com/item?id=7801834 One legitimate request is better installation of dependencies, which is in progress. This is not a 2 versus 3 issue, unless there are 3-only improvement. Some want concurrency primitives like go has. Guido went for a new module instead. I don't know what the importand differences are. Some want a better REPL, including color. The Idle shell already has the syntax colorizing. I don't know what else might have been meant. > "Python 3 is fine" http://sealedabstract.com/rants/python-3-is-fine/ In my opinion, about the best non-developer blog on Python 3 -- by a sensible, satisfied user. "in March 2014 Python 3 downloads overtook Python 2 downloads by a healthy margin 54% vs 46%." OK, that was boosted by the release of 3.4. But the point still stands. -- Terry Jan Reedy
[toc] | [prev] | [next] | [standalone]
| From | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2014-05-31 12:07 +0200 |
| Message-ID | <57ajo9poljjre4c4ig0n0ss8kph8k78lp0@4ax.com> |
| In reply to | #72180 |
On Wed, 28 May 2014 14:23:17 -0500, Larry Martell <larry.martell@gmail.com>
wrote:
>Somthing I came across in my travels through the ether:
>
>https://medium.com/@deliciousrobots/5d2ad703365d/
I just bought a new book on Python, since the one I had borrowed from my son
only dealt with Python 2.3, and everyone told me that was old.
So I bought this book, and decided that whatever version of Python it deals
with, that's the one I will download and use.
The book is:
Cunningham, Katie. 2014. Teach yourself Python in 24 hours.
Indianapolis: Sams.
ISBN: 978-0-672-33687-4
For Python 2.7.5
I'll leave Python 3.2 on my computer, but 2.7.5 will be the one I'm installing
now. Even if I could *find* a book that deals with Python 3.x, couldn't afford
to but yet another Python book.
--
Steve Hayes from Tshwane, South Africa
Web: http://www.khanya.org.za/stevesig.htm
Blog: http://khanya.wordpress.com
E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [prev] | [next] | [standalone]
| From | Johannes Bauer <dfnsonfsduifb@gmx.de> |
|---|---|
| Date | 2014-05-31 13:09 +0200 |
| Message-ID | <lmcd9q$tpb$1@news.albasani.net> |
| In reply to | #72331 |
On 31.05.2014 12:07, Steve Hayes wrote: > So I bought this book, and decided that whatever version of Python it deals > with, that's the one I will download and use. This sounds like remarkably bad advice. That's like saying "I bought a can of motor oil in my department store and whatever engine that is good for that's the car that I'll buy and put into!" > The book is: > > Cunningham, Katie. 2014. Teach yourself Python in 24 hours. > Indianapolis: Sams. > ISBN: 978-0-672-33687-4 > For Python 2.7.5 > > I'll leave Python 3.2 on my computer, but 2.7.5 will be the one I'm installing > now. Even if I could *find* a book that deals with Python 3.x, couldn't afford > to but yet another Python book. Lucky for you 2.7.5 isn't all that different from Py3 and most of it will apply. You'll be missing out on a bunch of cool features (arbitrary precision ints, int division operator, real Unicode support) but that's no big deal. Regards, Johannes -- >> Wo hattest Du das Beben nochmal GENAU vorhergesagt? > Zumindest nicht öffentlich! Ah, der neueste und bis heute genialste Streich unsere großen Kosmologen: Die Geheim-Vorhersage. - Karl Kaos über Rüdiger Thomas in dsa <hidbv3$om2$1@speranza.aioe.org>
[toc] | [prev] | [next] | [standalone]
| From | Stefan Behnel <stefan_ml@behnel.de> |
|---|---|
| Date | 2014-05-31 13:22 +0200 |
| Message-ID | <mailman.10507.1401535383.18130.python-list@python.org> |
| In reply to | #72333 |
Johannes Bauer, 31.05.2014 13:09: > Lucky for you 2.7.5 isn't all that different from Py3 and most of it > will apply. You'll be missing out on a bunch of cool features (arbitrary > precision ints Py2 has them as well (although they are called long). 1 << 300 gives the right answer in both Py2 and Py3, whether the result is a "long" or an "int". > int division operator AFAIR, that was added in Py2.5, so a book about Py2.7 should mention it somewhere. > real Unicode support Now, that is really something that has improved in Py3, and certainly a reason for many people to prefer Py3 over Py2. Stefan
[toc] | [prev] | [next] | [standalone]
| From | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2014-06-01 04:57 +0200 |
| Message-ID | <965lo9tqov049ldm9jlgukcchjonnh1m50@4ax.com> |
| In reply to | #72333 |
On Sat, 31 May 2014 13:09:45 +0200, Johannes Bauer <dfnsonfsduifb@gmx.de> wrote: >On 31.05.2014 12:07, Steve Hayes wrote: > >> So I bought this book, and decided that whatever version of Python it deals >> with, that's the one I will download and use. > >This sounds like remarkably bad advice. That's like saying "I bought a >can of motor oil in my department store and whatever engine that is good >for that's the car that I'll buy and put into!" No, it's a bit like flying in a Boeing 747 rather than a Concorde. The latyer may be later and more technically advanced and flew faster, but no one uses or supports it. > >> The book is: >> >> Cunningham, Katie. 2014. Teach yourself Python in 24 hours. >> Indianapolis: Sams. >> ISBN: 978-0-672-33687-4 >> For Python 2.7.5 >> >> I'll leave Python 3.2 on my computer, but 2.7.5 will be the one I'm installing >> now. Even if I could *find* a book that deals with Python 3.x, couldn't afford >> to but yet another Python book. > >Lucky for you 2.7.5 isn't all that different from Py3 and most of it >will apply. You'll be missing out on a bunch of cool features (arbitrary >precision ints, int division operator, real Unicode support) but that's >no big deal. I'm prepared to forgo whatever advantages those may have to avoid the frustration of example code not working and not knowing why. -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-06-01 13:35 +1000 |
| Message-ID | <mailman.10517.1401593718.18130.python-list@python.org> |
| In reply to | #72357 |
On Sun, Jun 1, 2014 at 12:57 PM, Steve Hayes <hayesstw@telkomsa.net> wrote: > On Sat, 31 May 2014 13:09:45 +0200, Johannes Bauer <dfnsonfsduifb@gmx.de> > wrote: > >>On 31.05.2014 12:07, Steve Hayes wrote: >> >>> So I bought this book, and decided that whatever version of Python it deals >>> with, that's the one I will download and use. >> >>This sounds like remarkably bad advice. That's like saying "I bought a >>can of motor oil in my department store and whatever engine that is good >>for that's the car that I'll buy and put into!" > > No, it's a bit like flying in a Boeing 747 rather than a Concorde. The latyer > may be later and more technically advanced and flew faster, but no one uses or > supports it. "Conky" is more like Python 1 - nobody uses it now (actually, there are more people using Python 1.x than flying Concorde), but it had its place in history. You're flying in a 747-400, which is fine, but when I want to go to England, I'd much rather go in a 777-300ER. (And yes, I've flown in both. Can't remember what model Queenie was, but with the 777s it's usually an Emirates 300ER.) The 747 is still functional, but no more functional than its era, and life's a lot better with the newer aircraft. If you want to start a brand new airline, you won't go for 747s if you can get 777s and A380s for the same price. For those who have 747s in their fleet, there's no problem - there'll be spare parts available from the manufacturer until at least donkey's years, and even after that, you can probably get third-party spare parts from some ex-Soviet mob (at least, they must be Soviets, why else would they wear red hats?); but you'll only get the features that were in the 747s when they were built, plus maybe some minor upgrades to the ancillary bits and pieces. Sure, you can get some of the fancy interior pieces that were designed for the 777s (enum, for instance), but the main hull isn't changing. So if you want to start a one-man airline (where you're managing the company, flying the plane, and everything else), do you start by looking at the relative merits of the 747-400 and 777-300ER and choosing, or do you poke around in your local second-hand shop for "Learn To Fly A Jet In Twenty-Four Hours" and see which cockpit it's showing photos of? There are courses for both types; both aircraft come with excellent "quick start" guides (see https://docs.python.org/2/tutorial/ and https://docs.python.org/3/tutorial/ ); and everything you want to ask about either type can be answered by the team of Boeing-List@Boeing.Org people, any hour of the day or night. All you're doing is picking your technology on the basis of *one* dead-tree book that you happen to have found. Is that really the most important deciding point? ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Rustom Mody <rustompmody@gmail.com> |
|---|---|
| Date | 2014-05-31 21:11 -0700 |
| Message-ID | <c82c95b2-ea3b-4e29-960c-72cff29a2b8b@googlegroups.com> |
| In reply to | #72360 |
On Sunday, June 1, 2014 9:05:11 AM UTC+5:30, Chris Angelico wrote: > So if you want to start a one-man airline (where you're managing the > company, flying the plane, and everything else), do you start by > looking at the relative merits of the 747-400 and 777-300ER I guess a person starting a one-man airline would be choosing a 7-15 seater and doing short to medium runs. Are there 7[47]7's in 7-15 seater range <wink>? And the earlier description of the choice for Word 97 reminded me of one of the 'prophet's' quotes from Illusions: <<Argue for your limitations and sure enough they are yours>> [Disclaimer: I was a Richard Bach fan in my youth]
[toc] | [prev] | [next] | [standalone]
| From | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2014-06-01 13:38 +0200 |
| Message-ID | <s34mo91dqb2d4im188enn7f0u2ih7n2t54@4ax.com> |
| In reply to | #72360 |
On Sun, 1 Jun 2014 13:35:11 +1000, Chris Angelico <rosuav@gmail.com> wrote: >Boeing-List@Boeing.Org people, any hour of the day or night. All >you're doing is picking your technology on the basis of *one* >dead-tree book that you happen to have found. Is that really the most >important deciding point? Yes. -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [prev] | [next] | [standalone]
| From | Bob Martin <bob.martin@excite.com> |
|---|---|
| Date | 2014-06-01 07:01 +0100 |
| Message-ID | <buvtuaF91bbU1@mid.individual.net> |
| In reply to | #72357 |
in 722929 20140601 035727 Steve Hayes <hayesstw@telkomsa.net> wrote: >No, it's a bit like flying in a Boeing 747 rather than a Concorde. The latyer >may be later and more technically advanced and flew faster, but no one uses or >supports it. Actually, the Concorde preceded the 747, and wasn't as "technically advanced", it was just faster.
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2014-06-01 07:52 +0100 |
| Message-ID | <mailman.10518.1401605574.18130.python-list@python.org> |
| In reply to | #72362 |
On 01/06/2014 07:01, Bob Martin wrote: > in 722929 20140601 035727 Steve Hayes <hayesstw@telkomsa.net> wrote: > >> No, it's a bit like flying in a Boeing 747 rather than a Concorde. The latyer >> may be later and more technically advanced and flew faster, but no one uses or >> supports it. > > Actually, the Concorde preceded the 747, and wasn't as "technically advanced", > it was just faster. > I recall Barnes Wallis slagging off the droop nose, but what did he know about aircraft? -- 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 | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2014-06-01 13:41 +0200 |
| Message-ID | <q74mo9hebfokqm5pfpqdhrje9m92801i4o@4ax.com> |
| In reply to | #72362 |
On Sun, 01 Jun 2014 07:01:46 BST, Bob Martin <bob.martin@excite.com> wrote: >in 722929 20140601 035727 Steve Hayes <hayesstw@telkomsa.net> wrote: > >>No, it's a bit like flying in a Boeing 747 rather than a Concorde. The latyer >>may be later and more technically advanced and flew faster, but no one uses or >>supports it. > >Actually, the Concorde preceded the 747, and wasn't as "technically advanced", >it was just faster. Boeing 747s were in airline service in 1970, Concorde didn't enter service till 4-5 years later. Not that it matters, it was just an analogy. I'm pretty certain that Python 2.x preceded Python 3.x -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2014-06-01 12:53 +0100 |
| Message-ID | <mailman.10522.1401623630.18130.python-list@python.org> |
| In reply to | #72372 |
On 01/06/2014 12:41, Steve Hayes wrote: > On Sun, 01 Jun 2014 07:01:46 BST, Bob Martin <bob.martin@excite.com> wrote: > >> in 722929 20140601 035727 Steve Hayes <hayesstw@telkomsa.net> wrote: >> >>> No, it's a bit like flying in a Boeing 747 rather than a Concorde. The latyer >>> may be later and more technically advanced and flew faster, but no one uses or >>> supports it. >> >> Actually, the Concorde preceded the 747, and wasn't as "technically advanced", >> it was just faster. > > Boeing 747s were in airline service in 1970, Concorde didn't enter service > till 4-5 years later. > > Not that it matters, it was just an analogy. I'm pretty certain that Python > 2.x preceded Python 3.x > Clearly you know nothing about the Python time machine :) -- 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 | alister <alister.nospam.ware@ntlworld.com> |
|---|---|
| Date | 2014-06-01 17:21 +0000 |
| Message-ID | <oiJiv.169923$i96.167685@fx11.am4> |
| In reply to | #72372 |
On Sun, 01 Jun 2014 13:41:33 +0200, Steve Hayes wrote: > On Sun, 01 Jun 2014 07:01:46 BST, Bob Martin <bob.martin@excite.com> > wrote: > >>in 722929 20140601 035727 Steve Hayes <hayesstw@telkomsa.net> wrote: >> >>>No, it's a bit like flying in a Boeing 747 rather than a Concorde. The >>>latyer may be later and more technically advanced and flew faster, but >>>no one uses or supports it. >> >>Actually, the Concorde preceded the 747, and wasn't as "technically >>advanced", >>it was just faster. > > Boeing 747s were in airline service in 1970, Concorde didn't enter > service till 4-5 years later. > Concord first flight march 2 1969 757 First flight Feb 9 1969 so there is not actually that much in it 747 entered service much sooner however > Not that it matters, it was just an analogy. I'm pretty certain that > Python 2.x preceded Python 3.x -- There seems no plan because it is all plan. -- C.S. Lewis
[toc] | [prev] | [next] | [standalone]
| From | Bob Martin <bob.martin@excite.com> |
|---|---|
| Date | 2014-06-02 07:14 +0100 |
| Message-ID | <bv2j30Fq0frU1@mid.individual.net> |
| In reply to | #72372 |
in 722944 20140601 124133 Steve Hayes <hayesstw@telkomsa.net> wrote: >On Sun, 01 Jun 2014 07:01:46 BST, Bob Martin <bob.martin@excite.com> wrote: > >>in 722929 20140601 035727 Steve Hayes <hayesstw@telkomsa.net> wrote: >> >>>No, it's a bit like flying in a Boeing 747 rather than a Concorde. The latyer >>>may be later and more technically advanced and flew faster, but no one uses or >>>supports it. >> >>Actually, the Concorde preceded the 747, and wasn't as "technically advanced", >>it was just faster. > >Boeing 747s were in airline service in 1970, Concorde didn't enter service >till 4-5 years later. Concorde design started in the early 50s, 747 mid-to-late 60s.
[toc] | [prev] | [next] | [standalone]
| From | Steven D'Aprano <steve+comp.lang.python@pearwood.info> |
|---|---|
| Date | 2014-05-31 12:30 +0000 |
| Message-ID | <5389cb53$0$29978$c3e8da3$5496439d@news.astraweb.com> |
| In reply to | #72331 |
On Sat, 31 May 2014 12:07:59 +0200, Steve Hayes wrote: > I'll leave Python 3.2 on my computer, but 2.7.5 will be the one I'm > installing now. Even if I could *find* a book that deals with Python > 3.x, couldn't afford to but yet another Python book. Version 2.7 is a good choice, and it will be around for a long time: it will be supported until at least 2020, so you should get many years of use from it. Do not be discouraged about Python 3. There are differences, but they aren't so different as to be a major barrier. By the time you have a bit of experience with 2.7, you will be more than capable of dealing with the differences with version 3. They are not different languages, think of them as slightly different dialects of the same language, like UK and South African English. -- Steven D'Aprano http://import-that.dreamwidth.org/
[toc] | [prev] | [next] | [standalone]
| From | wxjmfauth@gmail.com |
|---|---|
| Date | 2014-05-31 08:48 -0700 |
| Message-ID | <99b7b2a2-7521-42d7-a5a0-1a35d4d5b922@googlegroups.com> |
| In reply to | #72336 |
Le samedi 31 mai 2014 14:30:11 UTC+2, Steven D'Aprano a écrit : > On Sat, 31 May 2014 12:07:59 +0200, Steve Hayes wrote: > > > > > I'll leave Python 3.2 on my computer, but 2.7.5 will be the one I'm > > > installing now. Even if I could *find* a book that deals with Python > > > 3.x, couldn't afford to but yet another Python book. > > > > Version 2.7 is a good choice, and it will be around for a long time: it > > will be supported until at least 2020, so you should get many years of > > use from it. > > > > Do not be discouraged about Python 3. There are differences, but they > > aren't so different as to be a major barrier. By the time you have a bit > > of experience with 2.7, you will be more than capable of dealing with the > > differences with version 3. They are not different languages, think of > > them as slightly different dialects of the same language, like UK and > > South African English. > > > > ====== At least Py2 does not crash when using non ascii (eg sticking with cp1252). I just noticed this last week, Thursday, when presenting the absurdity of the Flexible String Representation. jmf
[toc] | [prev] | [next] | [standalone]
| From | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| Date | 2014-06-02 09:01 -0600 |
| Message-ID | <mailman.10561.1401721271.18130.python-list@python.org> |
| In reply to | #72339 |
[Multipart message — attachments visible in raw view] — view raw
On Jun 1, 2014 12:11 PM, <wxjmfauth@gmail.com> wrote: > At least Py2 does not crash when using non ascii > (eg sticking with cp1252). > > I just noticed this last week, Thursday, when presenting > the absurdity of the Flexible String Representation. So have you reported this alleged crash bug to the bug tracker? If not, then you're not contributing to Python or the discussion here in any useful way; you're just trolling.
[toc] | [prev] | [next] | [standalone]
Page 3 of 17 — ← Prev page 1 2 [3] 4 5 … 17 Next page →
Back to top | Article view | comp.lang.python
csiph-web