Terry Reedy wrote: >> hopefully, the Py3K distributors will use semi-automatic tools to download >> all they need to build a battery-included release. pushing all that over to >> the end users would be a major mistake. >> >> (python-dev and others could provide "profiles" for well-known and tested >> configurations; e.g. "psf standard", "scientific", "sumo", ...) > > I think this worth considering. The initial download for Internet Explorer > updates is less than a > megabyte. It looks at what you have and displays a menu of optional > components, and then > downloads and installs the 15-30 megabytes actually needed.
you misread my argument: I'm saying that the core Python distribution should be reasonably small (=smaller than today), but that we should provide a list of well-known/well-tested recommended packages that a distributor may want to include in their Python configuration, and a mechanism that they can use to get the packages, so they can include them in their distribution. we should also allow others to publish additional or alternative lists. (setuptools already contains most of the mechanisms needed for this, of course) if the distributor wants to ship the result as a sumo-installer, a highly granular set of RPM packages, an intelligent mini-installer, a bunch of eggs, or use some other approach is up to the distributor. </F> _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
