Re: Why Python 4.0 won't be like Python 3.0

From	Johann Hibschman <jhibschman@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: Why Python 4.0 won't be like Python 3.0
Date	2014-08-19 10:56 -0400
Organization	A noiseless patient Spider
Message-ID	<osxwqa4o7dy.fsf@gmail.com> (permalink)
References	(2 earlier) <mailman.13105.1408382076.18130.python-list@python.org> <lstq2t$pg5$1@reader1.panix.com> <53f29983$0$29986$c3e8da3$5496439d@news.astraweb.com> <lsvmsn$ahc$1@reader1.panix.com> <mailman.13152.1408459064.18130.python-list@python.org>

Show all headers | View raw

Skip Montanaro <skip@pobox.com> writes:

> On Tue, Aug 19, 2014 at 9:27 AM, Grant Edwards <invalid@invalid.invalid> wrote:
>> I'm probably conflating the 1.5.2/2.0 and the 2.6 stuff.  I do
>> remember delaying moving from 1.5.2 -> 2.0 until I really had to, but
>> I don't remember why.
>
> If you were a RedHat user during that timeframe, that might have
> contributed to your decision to delay. I no longer remember the
> details, but it was rather painful.

I vaguely remember holding off for a while until SWIG had 2.0 support,
or maybe Numeric lagged, or something, but that's getting pretty fuzzy.
There was definitely more there than, say, for 1.4 to 1.5.  It's hard to
believe that the Dubois/Hinsen/Hugunin article in Computers in Physics
(which was where I got my start with python) was a full 18 years ago.

Cheers,
Johann

Thread

Why Python 4.0 won't be like Python 3.0 Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-17 13:37 +0100
  Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-18 14:51 +0000
    Re: Why Python 4.0 won't be like Python 3.0 Chris Angelico <rosuav@gmail.com> - 2014-08-19 01:03 +1000
    Re: Why Python 4.0 won't be like Python 3.0 "ElChino" <elchino@cnn.cn> - 2014-08-18 19:00 +0200
      Re: Why Python 4.0 won't be like Python 3.0 Ethan Furman <ethan@stoneleaf.us> - 2014-08-18 10:15 -0700
      Re: Why Python 4.0 won't be like Python 3.0 Chris Angelico <rosuav@gmail.com> - 2014-08-19 09:46 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Ethan Furman <ethan@stoneleaf.us> - 2014-08-18 10:14 -0700
      Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-18 21:09 +0000
        Re: Why Python 4.0 won't be like Python 3.0 Emile van Sebille <emile@fenx.com> - 2014-08-18 14:45 -0700
        Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-19 10:25 +1000
          Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-19 14:27 +0000
            Re: Why Python 4.0 won't be like Python 3.0 Skip Montanaro <skip@pobox.com> - 2014-08-19 09:37 -0500
              Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-19 14:51 +0000
              Re: Why Python 4.0 won't be like Python 3.0 Johann Hibschman <jhibschman@gmail.com> - 2014-08-19 10:56 -0400
            Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-20 03:44 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Ben Finney <ben+python@benfinney.id.au> - 2014-08-19 08:27 +1000
      Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-19 11:00 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-19 10:05 +1000
      Re: Why Python 4.0 won't be like Python 3.0 Chris Angelico <rosuav@gmail.com> - 2014-08-19 10:30 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Tim Delaney <timothy.c.delaney@gmail.com> - 2014-08-19 10:47 +1000
  Re: Why Python 4.0 won't be like Python 3.0 wxjmfauth@gmail.com - 2014-08-19 12:04 -0700

csiph-web