. created to “bridge the gap between the shell and C” “never intended. . . to be the primary language for programmers.” Guido Van Rossum The Making of Python
simulation codes, data analysis packages, databases, visualization tools, and home-grown software-each of which presents the user with a different set of interfaces and file formats. As a result, a scientist may spend a considerable amount of time simply trying to get all of these components to work together in some manner...” - David Beazley Pythonista Extraordinaire Scientific Computing with Python (ACM vol. 216, 2000) Science Before Python . . .
of work processes. I would have Perl scripts that called C++ numerical routines that would dump data files, and I would load them up into MatLab to plot them. After a while I got tired of the MatLab dependency. . . so I started loading them up in GnuPlot.” -John Hunter creator of Matplotlib SciPy 2012 Keynote
heavily customized awk/sed/bash workflow to manage job submissions and postprocessing of C codes for supercomputing runs… So I used her scripts to run my jobs, and on top of that had added my own layer of Perl, plus a hefty amount of Gnuplot, IDL and Mathematica.” - Fernando Perez creator of IPython via email
Perl (for a year) and then Matlab and shell scripts & Fortran & C/C++ libraries. When I discovered Python, I really liked the language... But, it was very nascent and lacked a lot of libraries. I felt like I could add value to the world by connecting low-level libraries to high-level usage in Python.” - Travis Oliphant creator of NumPy & SciPy via email
language that is very powerful for developers, but is also accessible to Astronomers. Getting those two classes of people using the same tools, I think, provides a huge benefit that’s not always noticed or mentioned.” - Perry Greenfield Space Telescope Science Institute PyAstro 2015
question, and then she asked two. And each of those led her to three questions more, And some of those questions resulted in four. From Ada Twist, Scientist by Andrea Beaty & David Roberts Scientific Coding is Nonlinear and Exploratory
& Overlapping efforts Build on common projects Top-down planning Bottom-up/Loose organization Committee-oriented design Design by “doers” Endless analysis & argument Action-oriented & experimentation Unwilling to discard old tech Good at replacing old tech No leader to resolve conflicts BDFL resolves conflicts Adapted From Perry Greenfield’s PyData Keynote Python World Influencing Science . . . Python’s software practices increasingly adopted by academia