I had some experience with plone (and zope) - big, early python projects that formed a lot of the basis for package management and infrastructure for python. T

I had some experience with plone (and zope) - big, early python projects that formed a lot of the basis for package management and infrastructure for python. The "known good set" of packages as used by buildout for any given plone version were not really easy to work with. See eg: https://docs.plone.org/4/en/manage/troubleshooting/buildout.html#good-py-service https://docs.plone.org/4/en/manage/troubleshooting/buildout.... Which points to things like: http://dist.plone.org/release/3.3.5/versions.cfg http://dist.plone.org/release/3.3.5/versions.cfg Which aren't that much worse/better than a gemfile.lock for a rails project, I guess. Now, I guess the better answer is to have smaller projects, with different interfaces (eg: don't give all modulles/parts access to your zodb object database, have a ome json/rest interfaces etc). But apparently there are still many "big systems" being built.