Menu

#59 setup.py bug for linux

closed-invalid
nobody
5
2005-11-10
2005-09-23
Gal Koren
No

I've installed psyco 1.4 for linux from the source by
just typing:
python setup.py install
and it all went okay.
But take a look at this...

>>> import psyco
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "psyco/__init__.py", line 45, in ?
raise ImportError, str(e) + extramsg
ImportError: No module named _psyco (cannot locate the
compiled extension '_psyco.so' in the package path 'psyco')

_psyco.so is in the right place, it just that the
installation set it to have executable permission, and
so it could not be found by referencing it from a
local directory.
Writing "chmod auo-x ./_psyco.so" fixed the problem,
but it would be nicer if the installation wouldn't set
this permission in the first place.

Gal.

Discussion

  • Armin Rigo

    Armin Rigo - 2005-09-24

    Logged In: YES
    user_id=4771

    _psyco.so must have executable permissions. I don't know
    what you expect "the right place" for it to be, but I'm
    more inclined to think you've falled into a very common
    trap: having Python confuse a local 'psyco' directory with
    the installed one. Try to 'cd' anywhere unrelated and
    importing psyco again.

     
  • Armin Rigo

    Armin Rigo - 2005-11-10

    Logged In: YES
    user_id=4771

    Closing this bug report as invalid, but feel free to reopen it if you want to provide more information about it. (All so files in a Linux system are supposed to have the executable bit so I don't know what you mean.)

     
  • Armin Rigo

    Armin Rigo - 2005-11-10
    • status: open --> closed-invalid
     
  • Armin Rigo

    Armin Rigo - 2005-11-10

    Logged In: YES
    user_id=4771

    Closing this bug report as invalid, but feel free to reopen it if you want to provide more information about it. (All so files in a Linux system are supposed to have the executable bit so I don't know what you mean.)

     

Log in to post a comment.