5 ms·
> Python in the large is not very maintainable. Could you elaborate on that? I hear this a lot, but I work on a large Python project, and I don't think it is
by depressedpanda 9y ago
> Python in the large is not very maintainable.
Could you elaborate on that?
I hear this a lot, but I work on a large Python project, and I don't think it is hard to maintain. We do have some strict requirements, though:
1. Test coverage; if it's testable there must be tests for it
2. Type hinting; for large projects it's actually really nice to know at a glance what the expected type is
3. PEP8 & Pylint; how we write code should be standardized and easy for others to read
- skybrian 9y agoWell, (2) seems important and uncommon for Python in my experience, but it's been a while. Maybe it's more common these days? Here's the sort of scale I'm thinking of: consider a company with many teams, many apps, and many shared libraries. Some of the apps and libraries won't have anyone working on them, because it's generally not the case that a company is willing to fund maintenance forever on everything; people need to drop them for a while (to work on more important stuff) and someone else will come back to them later. (This is being "walk-away friendly".) Suppose you need to fix a security bug in a shared library and update all the apps, most of which you haven't seen before. How easy is that to do?