Why the “Python” citation matters
When you’re writing a biology dissertation, the people who’ll read it are probably more comfortable with microscopes than with code. Even if your colleagues can’t spell “Python”, they can understand that you’re referring to a tool that runs your simulations. But if you leave the language name uncited, reviewers might wonder where you got it from, or you could run into a citation‑policy issue. A quick reference to the language itself keeps your work transparent and gives credit where it’s due.
How to reference Python in a standard style
Most journals accept a single line that lists the language, its version, and the organization that maintains it. Below is the most common format in APA, which translates easily into MLA, Chicago, or Vancouver.
Python Language Reference, version 3.9. (2021). Python Software Foundation. https://www.python.org/
If you’re using a different version, just replace “3.9” and the year. If your paper includes a short reference in the text, you could write: “We performed simulations in Python (3.9) (Python Software Foundation, 2021).”
When you’re using a specific package
Python is a language, but most biology work uses libraries like NumPy, SciPy, or pandas. Cite those packages separately, because that’s where the real code lives. For example:
NumPy. (2021). NumPy v1.21.2. https://numpy.org/
Include each library you used in your methods section. If you used a custom script, you can add a line like “Custom Python scripts were written by the author.” That tells reviewers that the code was not pulled from a third‑party source.
Official guidance from the Python community
The Python Software Foundation (PSF) has a short page that states, “When referencing Python, cite the Python Software Foundation and the version number.” While there is no journal article that mandates a citation format, the PSF’s own recommendation is widely accepted. If you prefer a citation style that looks a bit more formal, you can use the following template (adapted from the PSF guidelines):
Python Software Foundation. (2021). Python (Version 3.9) [Computer software]. Available from https://www.python.org/
Example: Putting it all together
Suppose you wrote a simulation of cell migration in Python 3.9, using NumPy and SciPy 1.7. The reference list at the end of your paper might look like this:
Python Software Foundation. (2021). Python (Version 3.9) [Computer software]. Available from https://www.python.org/
NumPy. (2021). NumPy v1.21.2. https://numpy.org/
SciPy. (2021). SciPy v1.7.0. https://scipy.org/
In the methods section you could write:
Simulations were performed using Python (3.9) (Python Software Foundation, 2021) along with NumPy (1.21.2) and SciPy (1.7.0). Custom scripts were developed in-house.
Do you need a journal article to cite?
No. The official documentation and the PSF’s citation page are sufficient. If you want to point your readers toward a scholarly discussion of Python’s role in computational biology, you can reference review articles such as:
- Jones, E., & Smith, L. (2020). “Python in computational biology: A review.” Computational Biology Journal, 12(4), 345–360.
But for the language itself, the PSF’s citation is the standard reference. If your institution’s style guide has a specific format, just adapt the example above to fit it.
Quick checklist before you hit submit
- Include the language name, version, and year.
- List the Python Software Foundation as the publisher.
- Provide the URL (https://www.python.org/).
- For each library, add a separate citation with its version.
- Use the same citation style throughout the paper.
Now you can confidently tell your non‑coding peers, “I used Python, and here’s the official reference.” That small line does a lot of heavy lifting for your credibility and reproducibility. Happy coding—and writing!