At 11:29 PM 9/9/2005 -0300, Scott Kirkwood wrote:
>With Phillips's help I figured out the problem:
>
>[EMAIL PROTECTED]:~/scott/python/wxoptparse$ runWx
>Traceback (most recent call last):
> File "/usr/bin/runWx", line 4, in ?
> pkg_resources.run_script('wxOptParse==0.1.2', 'runWx')
> File
> "/usr/lib/python2.4/site-packages/setuptools-0.6a1c2-py2.4.egg/pkg_resources.py",
>
> line 407, in run_script
> self.require(requires)[0].run_script(script_name, ns)
> File
> "/usr/lib/python2.4/site-packages/setuptools-0.6a1c2-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 'runWx'
>[EMAIL PROTECTED]:~/scott/python/wxoptparse$ cd ..
>[EMAIL PROTECTED]:~/scott/python$ runWx
>usage: wxoptparse.py <programtorun>
>
>Basically, I was testing within my source directory and it was getting
>confused when it saw a folder called wxoptparse. The error was not very
>helpful in this case.
When testing, use 'setup.py develop' or 'setup.py test', and you won't have
this issue; the "develop" command sets up the scripts so they run from your
source tree, rather than trying to run them from an egg.
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
