no module named cli ? (when running any wdoc script)

1,956 views
Skip to first unread message

Shoola

unread,
Aug 31, 2009, 9:04:20 AM8/31/09
to Whoosh
this is the error i'm trying to run any wdoc script (exe, py, pyw,
etc)
i'm on windows
python 2.5
i installed using the following commands:
easy-install whoosh
easy-install wdoc[ui]
"old style" installaion from tar ball,
i have all reported dependencies,

but i keep getting this message.
what is CLI and where do i get it from??




C:\programs\Python\Scripts>wdoc-script.py index "asda"
Traceback (most recent call last):
File "C:\programs\Python\Scripts\wdoc-script.py", line 8, in
<module>
load_entry_point('whooshdoc==1.0', 'console_scripts', 'wdoc')()
File "C:\programs\Python\lib\site-packages\whooshdoc-1.0-py2.5.egg
\whooshdoc\app.py", line 106, in main
File "C:\programs\Python\lib\site-packages\whooshdoc-1.0-py2.5.egg
\whooshdoc\argcmd.py", line 87, in run
File "C:\programs\Python\lib\site-packages\whooshdoc-1.0-py2.5.egg
\whooshdoc\app.py", line 56, in index
File "C:\programs\Python\lib\site-packages\whooshdoc-1.0-py2.5.egg
\whooshdoc\indexem.py", line 10, in <module>
File "c:\programs\Python\Scripts\epydoc.py", line 5, in <module>
pkg_resources.run_script('epydoc==3.0.1', 'epydoc.py')
File "C:\programs\Python\Lib\site-packages\pkg_resources.py", line
448, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "C:\programs\Python\Lib\site-packages\pkg_resources.py", line
1166, in run_script
execfile(script_filename, namespace, namespace)
File "c:\programs\python\lib\site-packages\epydoc-3.0.1-py2.5-
win32.egg\EGG-INFO\scripts\epydoc.py", line 15, in <module>

from epydoc.cli import cli
ImportError: No module named cli

Marcus Puchalla

unread,
Aug 31, 2009, 9:55:12 AM8/31/09
to Whoosh


On 31 Aug., 15:04, Shoola <shula.amoks...@gmx.com> wrote:
> this is the error i'm trying to run any wdoc script (exe, py, pyw,
> etc)
> i'm on windows
> python 2.5
> i installed using the following commands:
> easy-install whoosh
> easy-install wdoc[ui]
> "old style" installaion from tar ball,
> i have all reported dependencies,
>
> but i keep getting this message.
> what is CLI and where do i get it from??
CLI is part of the epydoc module.
Get it and install it from:
http://epydoc.sourceforge.net/
I'm sorry but i don't know how to do this on Windows.
greets
Marcus

Jeroen Ruigrok van der Werven

unread,
Aug 31, 2009, 9:56:35 AM8/31/09
to who...@googlegroups.com
-On [20090831 15:55], Marcus Puchalla (c...@0xcb0.com) wrote:
>Get it and install it from:
>http://epydoc.sourceforge.net/
>I'm sorry but i don't know how to do this on Windows.

easy_install epydoc from cmd.exe works just as easily on Windows as on Unix.
:)

--
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Give me the strength to be who I was, and forgive me for who I am...

Robert Kern

unread,
Aug 31, 2009, 12:02:12 PM8/31/09
to who...@googlegroups.com
On Mon, Aug 31, 2009 at 06:04, Shoola<shula.a...@gmx.com> wrote:
>
> this is the error i'm trying to run any wdoc script (exe, py, pyw,
> etc)
> i'm on windows
> python 2.5
> i installed using the following commands:
> easy-install whoosh
> easy-install wdoc[ui]

Note that the latter is incorrect. The name of the package is
WhooshDoc, not wdoc.

> "old style" installaion from tar ball,
> i have all reported dependencies,
>
> but i keep getting this message.
> what is CLI and where do i get it from??

You seem to have an c:\programs\Python\Scripts\epydoc.py script from a
previous installation. When WhooshDoc goes to import the epydoc
package, it is getting picked up instead. If you installed epydoc via
easy-install, the script would have been installed as epydoc-script.py
(with an executable epydoc.exe to run it), and everything would have
been fine. Double-check to see that you have those files, then you can
remove c:\programs\Python\Scripts\epydoc.py.

--
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco

Shoola

unread,
Sep 1, 2009, 2:02:15 AM9/1/09
to Whoosh
ok, thanks.

i installed epydoc separately (there's a binary for windows in
sourceforge)
installed
but i still had to manually remove the epydoc (probably from earlier
isntallation)

note! i had to remove ALL these files
\python\scripts\epydoc.py
\python\scripts\epydoc.pyw
\python\scripts\epydoc.pyo
\python\scripts\epydoc.pyc

at once, since if .py doesnt exist python still imports the other
ones.



On Aug 31, 7:02 pm, Robert Kern <robert.k...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages