2022-07-14 –, Liffey B
One of the many strengths of python is PyPI, which complements and enhances the "batteries included" approach of the standard library. Building a library, and publishing it to PyPI has a number of challenges, pitfalls, and choices that someone has to make. In this talk, I would share my journey from v0.1.0 to v1.0.0 and all the moments that I said: "I wish I knew this thing before".
This talk is about all the mistakes that I made while building a library, how I would have avoided making them if I started today, what turns I would have taken differently, what choices I made, and why I made them. Examples are drawn from the building of a specific library, but it's not about a specific one.
The aim is to give some insights more into how to make choices when building a library available to the world, and less on the specific set of choices that I made.
It will not be technically challenging, but some familiarity with the Python ecosystem is advised.
none
Expected audience expertise: Python:some
Abstract as a tweet:The decisions made during the journey of a Python library from v0.1.0 to v1.0.0
Before becoming a software engineer, Stephanos used to be a number theorist, working on Arithmetic Geometry and Diophantine Equations. During his research, he realised his passion for coding and decided to pursue a career in it.
He is currently working as a Software Engineer at Piper, handling the infrastructure, the databases and the backend of the company.