Re: Stop writing Python 4 incompatible code

From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: Stop writing Python 4 incompatible code
Date	2016-01-14 14:08 +1100
Message-ID	<mailman.131.1452740906.13488.python-list@python.org> (permalink)
References	(2 earlier) <mailman.110.1452702751.13488.python-list@python.org> <5696e77e$0$1597$c3e8da3$5496439d@news.astraweb.com> <5d7a5bb1-f229-4755-a0bf-dd3ad9d99fba@googlegroups.com> <mailman.127.1452737481.13488.python-list@python.org> <6e0f3ba0-750d-4f57-afcc-238b85779948@googlegroups.com>

Show all headers | View raw

On Thu, Jan 14, 2016 at 1:51 PM, Rick Johnson
<rantingrickjohnson@gmail.com> wrote:
> On Wednesday, January 13, 2016 at 8:11:40 PM UTC-6, Michael Torrie wrote:
>> Hmm, so Guido moved to Dropbox because Google fired him?
>> [...] I can find zero evidence to support your assertion,
>
> Feel free to post evidence that will *DISPROVE* my statement.
>
>> Dishonesty is a harsh accusation, but when one makes up
>> stuff to support one's argument, is that not lying?
>
> You cannot accuse me of lying until you provide *PROOF* that
> i am lying.

That's not how it goes. You provided assertions; you should provide at
least some sort of supporting evidence.

> But even if you offered proof, that GvR was not
> fired because of Python's downward spiral, your implication
> that an "assertion" is "a lie" is in itself dishonest
> (yes?). And your interpretation of my statement "as
> malicious" does speak volumes to your true feelings on the
> subject. Why do you feel *SO* compelled to speak on behalf
> of GvR? And furthermore, what gives you the right to speak on
> his behalf?

You're talking about a very serious matter between two legal entities
- if someone was *fired* because of social, technological, or other
problems with Python, that has implications that could matter in a
court of law. So I put it right back to you: What gives you the right
to speak against Guido and Google?

>> Besides that, people leave good jobs all the time for
>> other more challenging jobs. Who says it was cushy?  Cushy
>> because Google paid him to work on Python?
>
> Getting paid to work on Pyhton 20% of the time is a pretty
> damn cushy job Micheal! How much time does *YOUR* employer
> pay *YOU* to work on "side projects"?

It's hardly a side project if it's creating something of immense value
to the company. And Google is still getting immense value from Python
even now that they're not paying Guido's salary.

And Michael's right: people move around for all sorts of reasons.
Doesn't necessarily mean anything about the previous job.

ChrisA

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