Member-only story
A Proposed Perfect Package Prototype for Python Projects
How to structure your Python package projects to ensure efficiency, effectiveness and future-proofing
Introduction
There are many options to consider and many decisions to make when laying out the structure of a Python package but once those design choices are committed to it is very difficult to make fundamental structural changes.
Also, if your users have started embedding the namespaces in their projects any changes you do make mean that those users will need to change their source code.
Therefore it is vital to make a good set of design and layout decisions for your packages at the outset.
The Problem
There are a lot of options for organising a Python package, hence it can be challenging to find the right design or at least one that will not cause issues later on.
The Opportunity
If a standard package layout can be established that addresses all the challenges and then prototyped in a skeleton project, creating future packages will be a quick and simple copy-and-paste.
