Title: In C++, I follow a playbook for keeping all hell from breaking loose:<p>1) Write a googletest
2) Write a googlebenchmark
3) Run all unit tests under AddressSanitizer, ThreadSanitizer, and g++ UB sanitizer
4) Tidy up with clang-format
5) Run cppcheck<p>So I feel pretty confident I&#x27;m not doing something braindead if I can get this stuff through CI.<p>But for Python, I don&#x27;t really have good idea when I&#x27;m doing something that&#x27;ll cause me agonizing pain in the future. The only tool I use is flake8, which is awesome, but I can&#x27;t see memory leaks or performance profiles.<p>What strategies do you adopt (and what tools do you use) to keep all hell from breaking loose in large Python projects?
Upvote: