Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #102504

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-26 23:56 +0100
Organization A noiseless patient Spider
Message-ID <o6dunt$9pj$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> <7f5a82f3-4b45-4b3f-aa65-85a4537fd73a@googlegroups.com>

Show all headers | View raw

On 26/01/17 21:49, Malcolm McLean wrote:
> On Thursday, January 26, 2017 at 3:14:26 PM UTC, David Brown wrote:
>>
>> And no, if you want to have an efficient implementation of big integer
>> multiplication in C you do /not/ start from the Python source code and
>> "peel off the Python bits".  You'll find there is no "interface layer"
>> in most of the Python library source code - it is much more integrated
>> to give the balance more of an emphasis on run-time speed than ease of
>> development.
>>
> A few years ago, someone decided to test a physics sim of a protein by
> asking two computational biochemistry labs to run it independently.
> They had supposedly separate programs. It emerged that 95% of the
> source code was in fact in common.
>
> That's the way it goes in scientific computing. Very few people have
> both the skills and the inclination to implement something from
> scratch when there is perfectly functional solution a short web
> search away.
>

That is true - but totally irrelevant to your accusations about the 
Python implementers.  In the case of the folks writing the Python 
run-time libraries, they /do/ have the skills and inclination to 
implement good code.  They were not trying to make two separate 
implementations.  And it is perfectly reasonable if they choose to make 
appropriate and legal use of existing libraries - which is not "stealing 
random code off the internet".

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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