The 20-Year Port: from PhD project to polished professional Python packaging @PyConAU
The 20-Year Port: from PhD project to polished professional Python packaging  @PyConAU
Uploaded August 2026 | Updated September 2026, 1 hour ago
(Paul Leopardi) Porting a scientific software library from a proprietary language to Python can potentially increase its user base, but the porting process itself can be tedious and error prone, and therefore cries out for automation, such as the use of AI coding agents. At the same time, scientific software libraries must be accurate, performant, easy to use, and easy to maintain. An over-reliance on automated tools can result in the software porting equivalent of AI slop: code that is unreliable and unmaintainable. The application of Research Software Engineering principles to the porting of scientific code can complement AI coding agents in preserving both academic rigour and thorough testing throughout the porting process, resulting in a reliable, well-tested and well-documented library.

In 2006, my mathematics PhD project resulted in a highly specialized geometrical toolbox that over the years has been used in diverse scientific and engineering applications. In 2013, at a SciPy conference, one of the attendees asked when the toolbox would be ported to Python.

On and off over a period of 20 years, I took that toolbox on a journey from an open source package within a proprietary mathematical software ecosystem to its current state as a polished, production-grade Python library. Firstly, in 2024, motivated by my deepening understanding of the diversity of its applications, I modernized the toolbox itself, including automating the testing of help examples. Next, in 2025, the rapid rise of Large Language Models as coding agents prompted me to undertake the long-delayed Python port. The coding agents did far more than a superficial translation of language syntax to Python. They improved the performance of the code by implementing improved algorithms, they converted the help examples into doctests, they created an automated test harness, they helped me to organize and improve the documentation, and they helped automate the PyPI release process.

https://2026.pycon.org.au/schedule/8LEEB7/

python, pycon, australia, programming, conference, technical, developers, panel, sessions, libraries, frameworks, community, sysadmins, students, education, data, science

Videos licensed as CC-BY-NC-SA 4.0

PyCon AU is the national conference for the Python programming community, bringing together professional, student and enthusiast developers, sysadmins and operations folk, students, educators, scientists, statisticians, and many others besides, all with a love for working with Python.

Licensed as CC BY-NC-SA - creativecommons.org/licenses/by-nc-sa/4.0

Produced by Next Day Video Australia: https://nextdayvideo.com.au

Fri Aug 28 15:55:00 2026 AEST (UTC+10) at Ballroom 1
The 20-Year Port: from PhD project to polished professional Python packagingReducing the Oops Factor: Pipelines for a Secure Python Development LifecycleFrom On-Prem to the Cloud and Back Again - Luke (PyCon AU 2026)Keeping Creativity the Focus in Visual Effects and Animation - Caitlin Wright (PyCon AU 2025)State of Exception(s) - Benno Rice (PyCon AU 2026)ML ain’t your only hammer: adding mathematical optimisation to the data scientist’s toolboxFalsehoods Programmers Believe About Reality - Lilly Ryan (PyCon AU 2025)Getting Started with Open Source Contributions - Stefanie Molin (Pycon AU 2024)Reinforcement Learning with Quantum Algorithms: Simulating Nematode BehaviourJust Enough Reliability - Shaun OKeefe (PyCon AU 2026)From Jupyter Notebook to Eruption: Getting Geohazard Research into ProductionBuilding an electricity market model from scratch - Dr Jack Simpson (PyCon AU 2025)
PyCon AU |

The 20-Year Port: from PhD project to polished professional Python packaging

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER