2 ms·
Well, (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 thin
by skybrian 9y ago
Well, (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?