paths.py not installed

Reported by Godisch-users on 2002-03-18
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Medium
Unassigned

Bug Description

# make install
Creating architecture independent directories...
[...]
Compiling /testing/mailman2.1/Mailman/versions.py ...
Traceback (most recent call last):
  File "bin/update", line 44, in ?
    import paths
ImportError: No module named paths
make: *** [update] Error 1
Exit 2

[http://sourceforge.net/tracker/index.php?func=detail&aid=531232&group_id=103&atid=100103]

Barry Warsaw (barry) wrote :

I can't reproduce this. Look at your make output and be
sure you don't have a permission problem somewhere.

Godisch-users (godisch-users) wrote :

Complete output attached...

Barry Warsaw (barry) wrote :

Something else weird is going on with your installation.
Why did you get this:

(cd email-1.2 ; /usr/bin/python setup.py --quiet install
--install-lib /opt/mailman2.1/pythonlib)
Traceback (most recent call last):
  File "setup.py", line 11, in ?
    from distutils.core import setup
ImportError: No module named distutils.core
make[1]: *** [install-packages] Error 1

i.e. why couldn't Python find distutils.core? Do you have
some weird PYTHONHOME envar setting? Try firing up Python
from the command line and importing distutils.core.

This failure is preventing the rest of misc/Makefile's
install target from completing, which is why bin/update
doesn't find paths.py.

Your Python installation looks messed up.

Godisch-users (godisch-users) wrote :

o.k. -- This seems to be a problem with Debian's Python
installation. I'll investigate and diskuss the matter there...

Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers