#1 error in line 212 upon execution

K Yoder

I dunno if this is bug or I'm just clueless about

I tried curator 1.1.2 and 1.2, and I get the same
message in both of them (using 1.1.2 the line number is
199 though):

Traceback (most recent call last):
File "/usr/local/bin/curator-1.2", line 212, in ?
from distutils.fancy_getopt \ ImportError: No module named distutils.fancy_getopt

It looks like I'm supposed to load some kind of Python
module? I checked the Python site for
"distutils.fancy_getopt" and found nothing.

Environment: Debian mixed releases (some stable, some
testing, some unstable), kernel 2.2.19pre17, Python
2.1.1, also tried with Python 2.2 and get same results.


  • K Yoder

    K Yoder - 2001-12-02

    Logged In: YES

    OK, I did some more digging and found out there's a
    "fancy_getopt" module I'm supposed to load. Can someone
    point me to its location? Google returns a bunch of docs,
    etc talking *about* this module, but not where I can
    download it.

    I installed the one that's in Debian stable; looks like it's
    for Python 1.5. So there's probably a different one for
    Pthon 2.1? I manually created a subdirectory of
    /usr/lib/python2.1/site-packages/ called "distutils" and
    into it, but still got this error.

    Yeah, yeah, this is turning more into a Python question, but
    can anyone here give me the "quick and dirty" answer?

  • Nobody/Anonymous

    Logged In: NO

    to solve your little problem, install (according your python version):
    * python1.5-distutils
    * python2.1-dev
    * python2.2-dev

    there you go..

  • Anonymous - 2003-01-29

    Logged In: YES

    a little re-post for the sake of warning the people
    monitoring this request. it seems i wasn't logged in on the
    previous one (and you did not receive an email as a result).

    so information available in the previous post

    ..and that was me :)

    kind regards,


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks