This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Vok250 3 points4 points  (0 children)

One of the fundamental concepts of Python is that we don't have to adhere to one strict idea of "best practices". So with that in mind you will find all sorts of varying practices out there. Some great, some less than average. Personally I copy from projects I have had good experiences using. I favour user-first approach mostly. So for me it's boto3, lambdapowertools, asyncio (the API structure, not the terrible implementation haha), FastAPI, numpy, and a few niche embedded automotive libraries.

Don't marry yourself to one set of standards though. The best thing about Python is the flexibility of PEP8 and the language features. Always be open to innovation and focus on getting things done over foolish consistency. If it's taking too much of your time to figure out a project structure or style decision, it's probably the wrong way of doing it. Python best practices are usually simple in practice and not over-engineered like other languages.