Stories
Slash Boxes
Comments

SoylentNews is people

posted by n1 on Tuesday May 13 2014, @01:11AM   Printer-friendly
from the it's-dark-in-here dept.

We all know that python is slower than compiled languages like C. But what can you do about it? Jake VanderPlas, director of research in the physical sciences for the university of Washington's eScience institute, digs into python's internals to explain how it works and what program design choices you can make to use python efficiently.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by LaminatorX on Tuesday May 13 2014, @04:21AM

    by LaminatorX (14) <{laminatorx} {at} {gmail.com}> on Tuesday May 13 2014, @04:21AM (#42533)

    The raw number crunching is slow, but the things I write in Python are network or disk access bound, not CPU bound. I can imagine a sufficiently large data set where that would shift, but in practice it's never happened.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2