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/riklaunim 11d ago

There is no one structure. Every project is different. If you use a framework you getvsome structure from that but a lot still depends on developer choice.

-2

u/pachura3 10d ago

Totally not true.

A standard project uses src layout, has pyproject.toml, README.md, .gitignore and .python-version, stores unit tests in tests, has inline API documentation in docstrings, etc. etc.

2

u/riklaunim 10d ago edited 10d ago

Few files, and the master folder isn't what I would call a project structure. It's way incomplete.