Ed Bennett - Structuring Large Python Projects

Hitchhiker's Guide to Python: docs.python-guide.org/en/lates...
Django: github.com/django/django
Openstack: github.com/openstack
Snakefood: furius.ca/snakefood/
Upcoming Tech Chats: sa2c.swansea.ac.uk/techchat/
========================================================
Abstract: What do you do when your Python projects become too large to manage by simply sticking a bunch of Python files in a folder? How can you nest packages to best make your code maintainable and reusable? In this talk I will discuss some best practices and strategies to structuring large projects, drawing from case studies in the Python standard library.

[@ruixue6955]

2:00 principle
2:40 use tests
2:55 documentation
3:56 use good structure
4:38 keep the root clean
4:45 README
4:51 LICENCE
5:00 requirements.txt (or pipfile)
5:11 tests/ (or tests.py)
5:22 doc
5:27 your_project_name/
5:31 some people create source directory, that is not so useful 5:38 because you will guess what's the main convention in this particular project
6:13 manage.py (Django)
6:41...
7:22 things to avoid
8:03 hidden coupling
10:22 spaghatti - very very long functions
10:49 ravioli (code)
11:27 more generic considerations
12:22 separate concerns with decorator

[@saikrishnavadali05]

Great Presentation!! Learnt many important python structuring concepts from this presentation. Thanks to Swansea academy and Ed Bennett

[@augustvanhout2163]

Thanks, have an upvote. Learning for work in a logistics company to do basic data science, and will use these principles to keep it professional. Thanks for your work.

[@sethgrayson2470]

Great talk! Very useful.

[@chaitanyakrishna8468]

Great presentation with explanation ,it helped me a lot in making hasslefree arrangement of python file structuring!!