move extension into package - without relative imports.

[mindw]

No description provided.

[giampaolo]

Changing the C extension path in setup.py causes the same problem I described in #578 (importing psutil from its root source directory):

>>> import psutil
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "psutil/__init__.py", line 63, in <module>
    from psutil import _pslinux as _psplatform
  File "psutil/_pslinux.py", line 26, in <module>
    import psutil._psutil_linux as cext
ImportError: No module named _psutil_linux
>>> 

I think there's no way around that.

[mindw]

Did you do setup.py build_ext -f -i before opening the prompt?
On Feb 9, 2015 1:07 PM, "giampaolo" [email protected] wrote:

Changing the C extension path in setup.py causes the same problem I
described in #578 #578
(importing psutil from its root source directory):

import psutil
Traceback (most recent call last):
File "", line 1, in
File "psutil/init.py", line 63, in
from psutil import _pslinux as _psplatform
File "psutil/_pslinux.py", line 26, in
import psutil._psutil_linux as cext
ImportError: No module named _psutil_linux

I think there's no way around that.

—
Reply to this email directly or view it on GitHub
#587 (comment).

[giampaolo]

setup.py build_ext -i did the trick. I reapplied your original changes. Thanks a lot.