ajones wrote: > > Downloaded the eggs from turbogears.org/download/ (had to get > setuptools from the cheeseshop as the download page had a development > version) > Modify ez_setup.py so that DEFAULT_URL pointed to > "file:C:/path/to/download/directory/" > Run ez_setup.py like normal using -f c:/path/to/download/directory/ > > Why the need to specify this location in two different places? I am > assuming that the -f argument indicates the file source, if so why does > the system seem to use DEFAULT_URL exclusively?
ez_setup.py is a bootstrap script used to install setuptools only. It has extremely limited intelligence and is mainly intended to be imported by a setup script (i.e., a setup.py file). As you will see from the docstrings, a script can call use_setuptools() with a different default URL and version. Anyway, it is designed only to download a setuptools egg from a known absolute URL, and then pass command-line arguments on to easy_install once setuptools is bootstrapped. The normal way to use a setuptools egg you've already downloaded with ez_setup.py would be to just put the egg in the current directory. ez_setup.py detects when the requested version of the setuptools egg is present in the current directory, and will use it without downloading. In other words, you're trying too hard. :) Just put the setuptools egg in the current directory and run ez_setup.py. DEFAULT_URL is used *only* to download the setuptools egg, and it has nothing whatsoever to do with -f/--find-links; it does not work in the same way at all. -f is used for *finding* things without a known download URL, and the code that does that is in the setuptools egg; ez_setup.py doesn't have that code or all the other easy_install features built in, because then it would be as big as setuptools itself. :) It just *seems* to have those features because once setuptools is bootstrapped, it passes the command-line arguments on to easy_install.
