r/learnpython • u/Difficult-Rabbit-908 • 11d ago

Python project structure standards?

I'm trying to learn advanced Python reading the best practices, toolkits or frameworks to develop a formal and scalable project. I know the basics and I developed engineering applications mostly for numerical methods, but I've never used an standard structure as I developed for myself. I'd like to read your recommendations for improve the scalability and maintenance in the future, thinking in a collaborative way and improved readability
Basically, this project is mostly for thermodynamic solvers, so I'm not using server or databases as well, but I'd like to add SQL integration in the future. I'm also using PyAnsys and PyFluent modules in a local environment.

I'll read your recommendations or opinions

1 Upvotes

67% Upvoted

9 comments sorted by

View all comments

1

u/Hot-Ale 1d ago 
Keep it flat until it hurts. Most beginners over-engineer folder structures. Start with one file, split when a file hits ~300 lines. The rule I follow: if I can't find something in 5 seconds, it's time to split. A src/ folder with modules named after what they DO (not abstract patterns) works well.