Re: Why Python is slow

From	David Brown <david.brown@hesbynett.no>
Newsgroups	comp.lang.c
Subject	Re: Why Python is slow
Date	2017-01-27 09:31 +0100
Organization	A noiseless patient Spider
Message-ID	<o6f0e7$hb$1@dont-email.me> (permalink)
References	(1 earlier) <expression-20170124202746@ram.dialup.fu-berlin.de> <o69r1u$s39$1@dont-email.me> <5fa6528c-ecf9-451e-9cf2-c44d16a83f3d@googlegroups.com> <o6d3l5$gc5$1@dont-email.me> <lntw8lcssu.fsf@kst-u.example.com>

Show all headers | View raw

On 27/01/17 00:20, Keith Thompson wrote:
> David Brown <david.brown@hesbynett.no> writes:
>> On 26/01/17 15:44, Malcolm McLean wrote:
> [...]
>>> The Python source code has generally been stolen from reference
>>> implementations which have been floating around in cyberspace for
>>> ages.
>>
>> By "stolen", can I assume you are accusing the Python implementation
>> developers of making illegal unlicensed copies of other people's code,
>> breaking their licences, copyrights, or in some other way offending the
>> original authors' rights?  Obviously you can't really mean "stolen",
>> because that does not make sense for something like source code.
> [...]
> 
> David, sometimes the word "stolen" is used facetiously to refer to
> reusing existing code, even if such reuse is perfectly legitimate.
> I've used the word that way myself on occasion.  It's possible,
> but by no means certain, that Malcolm meant it that way.

Yes, I realise that - and I expect that is the usage Malcolm meant.  And
that's fine in an appropriate context - we have all "stolen" sample code
from the net in that manner.

My objection with Malcolm's writing is that he is blatantly accusing the
Python library implementers of just grabbing whatever code they found
lying about, without consideration for quality, suitability, copyrights,
licenses, or anything else, then slapping on a "Python wrapper".  Now, I
know some people /do/ work like that, and I have not examined the Python
source code to look at how it was made - but I think Malcolm's comments
are way out of line unless he can provide justification for them.

> 
> Malcolm, please clarify either that you are, or that you are not,
> accusing the Python developers of doing something illegal and/or
> illegitimate.
>

Thread

Why Python is slow thunderbirdmember@gmail.com - 2017-01-24 10:22 -0800
  Re: Why Python is slow Richard Heathfield <rjh@cpax.org.uk> - 2017-01-24 18:33 +0000
  Re: Why Python is slow Richard Heathfield <rjh@cpax.org.uk> - 2017-01-24 20:14 +0000
    Re: Why Python is slow luser droog <luser.droog@gmail.com> - 2017-01-26 10:13 -0800
    Re: Why Python is slow Tim Rentsch <txr@alumni.caltech.edu> - 2017-01-30 05:50 -0800
  Re: Why Python is slow bart4858@gmail.com - 2017-01-24 13:21 -0800
  Re: Why Python is slow BartC <bc@freeuk.com> - 2017-01-24 22:23 +0000
  Re: Why Python is slow "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-24 17:11 -0800
    Re: Why Python is slow "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-24 19:26 -0800
    Re: Why Python is slow "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-25 12:50 -0800
      Re: Why Python is slow BartC <bc@freeuk.com> - 2017-01-25 21:52 +0000
        Re: Why Python is slow "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-25 14:30 -0800
          Re: Why Python is slow BartC <bc@freeuk.com> - 2017-01-25 22:59 +0000
            Re: Why Python is slow "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-27 13:20 -0800
      Re: Why Python is slow DFS <nospam@dfs.com> - 2017-01-25 19:22 -0500
        Re: Why Python is slow "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-26 13:40 -0800
  Re: Why Python is slow David Brown <david.brown@hesbynett.no> - 2017-01-25 10:29 +0100
    Re: Why Python is slow gazelle@shell.xmission.com (Kenny McCormack) - 2017-01-25 10:38 +0000
    Re: Why Python is slow Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-26 06:44 -0800
      Re: Why Python is slow Richard Heathfield <rjh@cpax.org.uk> - 2017-01-26 15:00 +0000
        Re: Why Python is slow Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-26 17:23 +0000
          Re: Why Python is slow supercat@casperkitty.com - 2017-01-26 09:42 -0800
            Re: Why Python is slow Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-26 18:24 +0000
      Re: Why Python is slow David Brown <david.brown@hesbynett.no> - 2017-01-26 16:14 +0100
        Re: Why Python is slow Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-26 12:49 -0800
          Re: Why Python is slow Robert Wessel <robertwessel2@yahoo.com> - 2017-01-26 15:11 -0600
          Re: Why Python is slow David Brown <david.brown@hesbynett.no> - 2017-01-26 23:56 +0100
        Re: Why Python is slow Keith Thompson <kst-u@mib.org> - 2017-01-26 15:20 -0800
          Re: Why Python is slow David Brown <david.brown@hesbynett.no> - 2017-01-27 09:31 +0100
      Re: Why Python is slow fir <profesor.fir@gmail.com> - 2017-01-27 07:24 -0800
        Re: Why Python is slow fir <profesor.fir@gmail.com> - 2017-01-27 07:57 -0800
          Re: Why Python is slow fir <profesor.fir@gmail.com> - 2017-01-27 08:46 -0800
        Re: Why Python is slow supercat@casperkitty.com - 2017-01-27 08:06 -0800
          Re: Why Python is slow fir <profesor.fir@gmail.com> - 2017-01-27 08:39 -0800
            Re: Why Python is slow fir <profesor.fir@gmail.com> - 2017-01-27 13:29 -0800
  Re: 3**3**3**3 Noob <root@127.0.0.1> - 2017-01-27 14:33 +0100

csiph-web