On 10/13/05, Tim Lesher <[EMAIL PROTECTED]> wrote:
> Worse, running 'easy_install.py --upgrade setuptools' _broke_
> setuptools--afterwards, running easy_install.py yields this:
>
> Traceback (most recent call last):
> File "c:\Python24\Scripts\easy_install.py", line 4, in ?
> pkg_resources.run_script('setuptools==0.6a1', 'easy_install.py')
> File
> "c:\python24\lib\site-packages\setuptools-0.6a5-py2.4.egg\pkg_resources.py",
> line 407, in run_script
> self.require(requires)[0].run_script(script_name, ns)
> File
> "c:\python24\lib\site-packages\setuptools-0.6a5-py2.4.egg\pkg_resources.py",
> line 914, in run_script
> raise ResolutionError("No script named %r" % script_name)
> pkg_resources.ResolutionError: No script named 'easy_install.py'
>
> Perhaps setuptools just has problems updating files in the scripts
> directory on Windows?
I *thought* that setuptools creates both .py and .exe files, but I
could be wrong. It's possible that easy_install.exe is the only
functional one after the setuptools upgrade. (Which reminds me, the
download page needs to be updated to just say easy_install and not
easy_install.py...)
If you didn't end up with a tg-admin.exe file in your scripts
directory, then I should change the instructions to recommend using
ez_setup rather than easy_install.
Kevin
