I follow your instuctions exactly, I never typed the ".py", that's just
in the error I get. I should have shown the whole error. Here it is
(following the command):

C:\Documents and Settings\Radmila\Desktop\holdemdata>easy_install -f
http://www.turbogears.org/download/index.html TurboGears
Traceback (most recent call last):
  File "C:\Python24\Scripts\easy_install.py", line 4, in ?
    pkg_resources.run_script('setuptools==0.6a5', 'easy_install.py')
  File
"c:\python24\lib\site-packages\setuptools-0.6a5-py2.4.egg\pkg_resources.p
y", 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.p
y", line 914, in run_script
    raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'easy_install.py'

I should also mention that the "easy_install -U setuptools" command
*did* seem to work except for a funny bit at the end where it could not
find the package named "-". I'm sorry I don't recall exactly. Now, when
I run this command, I get the same "No script named..." error as above.

Clearly, easy_install.py (in my Scripts folder) is being called because
when I rename it I get the following error instead:

'renamed.py' is not recognized as an internal or external command,
operable program or batch file.

Hope this helps.

Steve







'asdad.py' is not recognized as an internal or external command,
operable program or batch file.

Kevin Dangoor wrote:
> On 10/14/05, Stephen Day <[EMAIL PROTECTED]> wrote:
> >
> > Now I'm getting an error: No script named "easy_install.py".
>
> It should be just "easy_install".
>
> Here's what happened between setuptools 0.6a1 and 0.6a5:
>
> setuptools now knows how to generate scripts for you if your script is
> nothing but a call to a main function somewhere. That's what
> turbogears-admin.py was, so it made sense to eliminate the separate py
> file and let setuptools generate it.
>
> Additionally, setuptools creates the script as a nice, ready-to-run
> program for your platform. It's either a .exe on Windows or an
> executable script on unixes and Mac OS. So, after the setuptools
> upgrade, there is no more ".py" needed to run the scripts.
>
> Kevin
>
> --
> Kevin Dangoor
> Author of the Zesty News RSS newsreader
>
> email: [EMAIL PROTECTED]
> company: http://www.BlazingThings.com
> blog: http://www.BlueSkyOnMars.com

Reply via email to