Re: Stop writing Python 4 incompatible code

Newsgroups	comp.lang.python
Date	2016-01-14 07:30 -0800
References	(5 earlier) <mailman.127.1452737481.13488.python-list@python.org> <6e0f3ba0-750d-4f57-afcc-238b85779948@googlegroups.com> <mailman.131.1452740906.13488.python-list@python.org> <ed119cca-3cff-4738-92a3-58b2d5c314cf@googlegroups.com> <mailman.132.1452748731.13488.python-list@python.org>
Message-ID	<7df87f88-b63d-4cc2-95a9-075313d72537@googlegroups.com> (permalink)
Subject	Re: Stop writing Python 4 incompatible code
From	Rick Johnson <rantingrickjohnson@gmail.com>

Show all headers | View raw

On Wednesday, January 13, 2016 at 11:19:16 PM UTC-6, Michael Torrie wrote:

> The only one speculating is you.  Everything I've read points to this
> idea of yours about GvR and Google being untrue.  

Providing speculation is not the same as providing facts.
Please provide facts. And enumerate them!

> You have presented no evidence for your accusation, so
> given the evidence I have seen that contradicts you, I
> must conclude that you made it [up]. 

Here is an enumerated list of the indisputable facts of this
case:

  (1) GvR is no longer employed by Google (FACT!)

  (2) Before Python3 came along, the Python community was
  vibrant and growing (FACT!)

  (3) After Python3 came along, the Python community has
  become fractured, and the Python code base has become
  fractured, and the general public consensus is that Python
  is on its way to extinction (FACT!)

Of course these are not *ALL* the facts, but they are *ALL*
the facts that publicly available. If you (and your hero
GvR) want to prevent rumors from circulation, them i
suggest you provide the relevant facts regarding his change
of employment, and simply throwing opinions out that "the
change suited him well" is not providing any facts.

> I don't know who the "we" you're talking about is, 

I represent the concerns of entire class of Python community
members, folks who are fearful to speak out publicly for
fear of reprisals (which is a legitimate fear).

> but if your livelihood depends on Python's existence and
> development in a certain direction, then [...] you should
> be able to adapt to any programming language suitable for
> your job at hand.

Both myself, and the people i represent, write code in
*MANY* languages, but to suggest that we should just """be
quiet and translate millions of lines of code into another
language because our "dear leader" decided to break
backwards compatibility for arbitrary reasons"""... is a
quite impractical, don't you think?

Thread

Stop writing Python 4 incompatible code Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-01-13 18:30 +1100
  Re: Stop writing Python 4 incompatible code sjmsoft@gmail.com - 2016-01-13 06:21 -0800
    Re: Stop writing Python 4 incompatible code Random832 <random832@fastmail.com> - 2016-01-13 11:25 -0500
      Re: Stop writing Python 4 incompatible code Steven D'Aprano <steve@pearwood.info> - 2016-01-14 11:10 +1100
        Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-13 22:40 -0200
          Re: Stop writing Python 4 incompatible code Steven D'Aprano <steve@pearwood.info> - 2016-01-14 12:02 +1100
            Re: Stop writing Python 4 incompatible code Michael Torrie <torriem@gmail.com> - 2016-01-13 18:24 -0700
            Re: Stop writing Python 4 incompatible code Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-01-13 21:39 -0500
            Re: Stop writing Python 4 incompatible code Gene Heskett <gheskett@wdtv.com> - 2016-01-13 21:59 -0500
            Re: Stop writing Python 4 incompatible code Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-01-14 07:41 -0500
            Re: Stop writing Python 4 incompatible code Peter Otten <__peter__@web.de> - 2016-01-14 14:43 +0100
            Re: Stop writing Python 4 incompatible code "D'Arcy J.M. Cain" <darcy@VybeNetworks.com> - 2016-01-14 08:47 -0500
            Re: Stop writing Python 4 incompatible code Peter Otten <__peter__@web.de> - 2016-01-14 16:32 +0100
            Re: Stop writing Python 4 incompatible code "D'Arcy J.M. Cain" <darcy@VybeNetworks.com> - 2016-01-14 10:47 -0500
            Re: Stop writing Python 4 incompatible code Peter Otten <__peter__@web.de> - 2016-01-14 17:52 +0100
            Re: Stop writing Python 4 incompatible code Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-01-15 16:08 +1300
              Re: Stop writing Python 4 incompatible code Chris Angelico <rosuav@gmail.com> - 2016-01-15 15:56 +1100
                Re: Stop writing Python 4 incompatible code Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-01-16 10:02 +1300
              Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-15 09:40 -0200
          Re: Stop writing Python 4 incompatible code Robin Koch <robin.koch@t-online.de> - 2016-01-15 19:29 +0100
            Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-15 16:43 -0200
        Re: Stop writing Python 4 incompatible code Terry Reedy <tjreedy@udel.edu> - 2016-01-13 19:53 -0500
        Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-13 17:02 -0800
          Re: Stop writing Python 4 incompatible code Chris Angelico <rosuav@gmail.com> - 2016-01-14 12:29 +1100
          Re: Stop writing Python 4 incompatible code Michael Torrie <torriem@gmail.com> - 2016-01-13 19:11 -0700
            Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-13 18:51 -0800
              Re: Stop writing Python 4 incompatible code Chris Angelico <rosuav@gmail.com> - 2016-01-14 14:08 +1100
                Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-13 19:29 -0800
                Re: Stop writing Python 4 incompatible code Michael Torrie <torriem@gmail.com> - 2016-01-13 22:18 -0700
                Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-14 07:30 -0800
                Re: Stop writing Python 4 incompatible code Chris Angelico <rosuav@gmail.com> - 2016-01-15 04:41 +1100
                Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-14 10:40 -0800
                Re: Stop writing Python 4 incompatible code <paul.hermeneutic@gmail.com> - 2016-01-14 13:16 -0700
                Re: Stop writing Python 4 incompatible code Steven D'Aprano <steve@pearwood.info> - 2016-01-15 09:04 +1100
                Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-14 15:16 -0800
                Re: Stop writing Python 4 incompatible code Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-01-14 19:16 +1100
                Re: Stop writing Python 4 incompatible code wxjmfauth@gmail.com - 2016-01-14 01:37 -0800
          Re: Stop writing Python 4 incompatible code Terry Reedy <tjreedy@udel.edu> - 2016-01-14 00:45 -0500
            Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-14 07:52 -0800
              Re: Stop writing Python 4 incompatible code Ian Kelly <ian.g.kelly@gmail.com> - 2016-01-14 15:52 -0700
                Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-14 15:55 -0800
                Re: Stop writing Python 4 incompatible code Emile van Sebille <emile@fenx.com> - 2016-01-15 06:52 -0800
                Re: Stop writing Python 4 incompatible code Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-01-16 09:49 +1300
                Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-15 14:34 -0800
                Re: Stop writing Python 4 incompatible code Rick Johnson <rantingrickjohnson@gmail.com> - 2016-01-15 13:45 -0800
                Re: Stop writing Python 4 incompatible code William Ray Wing <wrw@mac.com> - 2016-01-15 12:02 -0500
                Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-15 16:09 -0200
                Re: Stop writing Python 4 incompatible code Alister <alister.ware@ntlworld.com> - 2016-01-15 18:46 +0000
                Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-15 16:55 -0200
                Re: Stop writing Python 4 incompatible code Alister <alister.ware@ntlworld.com> - 2016-01-16 14:41 +0000
                Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-16 12:48 -0200
                Re: Stop writing Python 4 incompatible code paul.hermeneutic@gmail.com - 2016-01-16 09:08 -0700
                Re: Stop writing Python 4 incompatible code William Ray Wing <wrw@mac.com> - 2016-01-16 13:00 -0500
                Re: Stop writing Python 4 incompatible code Michael Torrie <torriem@gmail.com> - 2016-01-16 12:26 -0700
                Re: Stop writing Python 4 incompatible code Chris Angelico <rosuav@gmail.com> - 2016-01-17 13:43 +1100
                Re: Stop writing Python 4 incompatible code William Ray Wing <wrw@mac.com> - 2016-01-15 13:49 -0500
                Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-15 16:53 -0200
                Re: Stop writing Python 4 incompatible code Mark Lawrence <breamoreboy@yahoo.co.uk> - 2016-01-15 20:58 +0000
                Re: Stop writing Python 4 incompatible code Christopher Reimer <christopher_reimer@icloud.com> - 2016-01-15 14:09 -0800
                Re: Stop writing Python 4 incompatible code Christopher Reimer <christopher_reimer@icloud.com> - 2016-01-16 20:51 -0800
    Re: Stop writing Python 4 incompatible code Chris Angelico <rosuav@gmail.com> - 2016-01-14 03:38 +1100
  Re: Stop writing Python 4 incompatible code Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-01-14 10:38 +1300
    Re: Stop writing Python 4 incompatible code Bernardo Sulzbach <mafagafogigante@gmail.com> - 2016-01-13 19:46 -0200
  Re: Stop writing Python 4 incompatible code BartC <bc@freeuk.com> - 2016-01-14 01:02 +0000
    Re: Stop writing Python 4 incompatible code Chris Angelico <rosuav@gmail.com> - 2016-01-14 12:21 +1100
      Re: Stop writing Python 4 incompatible code BartC <bc@freeuk.com> - 2016-01-14 01:49 +0000

csiph-web