....at least around here.\n\nI run a corporate Open Source Software Toolkit, which makes hundreds\nof libraries and apps available to thousands of technical employees.\nThe rules are that a) a very few authorized downloaders obtain\ntarballs and put them in a depot and b) other users get tarballs from\nthe depot and build from source.\n\nHistorically, python packages played well in this context. Install\nwas a simple download, untar, setup.py build/install.\n\nEggs and with other setuptools-inspired install processes break this\nparadigm. The tarballs are incomplete in the first place. The builds\nsometimes wander off to the internet looking for more downloads. The\ninstalls sometimes wander off to the internet looking for\ncompatibility conditions. (Or rather they try to do so and fail\nbecause I don't let themn through the firewall.)\n\nThese are unacceptable behaviors. I am therefore dropping ZODB3, and\nam considering dropping TurboGears and ZSI. If the egg paradigm\nspreads, yet more packages will be dropped (or will never get a chance\nto compete for addition).\n\nI've asked before, and I'll ask again: If you are doing a Python\nproject, please make a self-sufficient tarball available as well. You\ncan have dependencies, as long as they are documented and can be\nobtained by separate manual download. \n\nThanks for listening.