Project and python specific standards that have been chosen and not otherwise explicitly recommended.
Where possible, follow our practices. See:
Generally use Robert Martin's three laws of TDD:
- Only write enough of a unit test to fail.
- Only write production code to make a failing unit test pass.
Where possible, minimize the number of package dependencies used to get the job done. If it's a complex task and someone else has an appropriately licensed solution which is carefully maintained and largely established, then it's a good idea.
Use SOLID design principles and keep it stupid simple.
Generally heroku's The Twelve-Factor App guide should be followed.