On Sat, Dec 19, 2009 at 03:10:24PM -0800, Paul Nguyen (SysOps) wrote:
> I'm a new to PSI. I cloned the tree from the mercurial repository at
> bitbucket. I am running RHEL 5.4 x86_64 with the stock python. I built the
> libraries and ran the tests, and came up with just one failure.
>
> ======================================================================
> FAIL: test_free (mount_test.MountAttrTests)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/root/psi/tests/mount_test.py", line 136, in test_free
> self.assert_(self.m.total > self.m.free)
> AssertionError
>
> ----------------------------------------------------------------------
> Ran 159 tests in 1.638s
>
> FAILED (failures=1)
I've seen this failure once before I think. It's strange but nothing
to worry about too much. But I've just pushed a changeset out that
should give us some more information about why this test fails, so if
you want to re-run this and send the output again that would be nice.
> When I go to the python interpreter and try to import the psi module, it
> fails with the following message.
[...]
> >>> import psi
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "psi/__init__.py", line 43, in ?
> from psi._psi import AttrNotAvailableError, AttrInsufficientPrivsError,
> \
> ImportError: No module named _psi
This is simply the python import path that is surprising you. If you
check your sys.path you will notice that the current directory is on
it, and your current directory -the psi toplevel directory- has the
pure-python source of psi inside the psi/ directory. When python
tries to use that it is missing the extension modules.
If you want to try psi without installing it you can just cd into the
build/lib.linux-x86_64-2.6/ (or whatever it is for your system)
directory before starting python.
Regards
Floris
--
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org
Hi Paul
I've seen this failure once before I think. It's strange but nothing
On Sat, Dec 19, 2009 at 03:10:24PM -0800, Paul Nguyen (SysOps) wrote:
> I'm a new to PSI. I cloned the tree from the mercurial repository at
> bitbucket. I am running RHEL 5.4 x86_64 with the stock python. I built the
> libraries and ran the tests, and came up with just one failure.
>
> ======================================================================
> FAIL: test_free (mount_test.MountAttrTests)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/root/psi/tests/mount_test.py", line 136, in test_free
> self.assert_(self.m.total > self.m.free)
> AssertionError
>
> ----------------------------------------------------------------------
> Ran 159 tests in 1.638s
>
> FAILED (failures=1)
to worry about too much. But I've just pushed a changeset out that
should give us some more information about why this test fails, so if
you want to re-run this and send the output again that would be nice.
> When I go to the python interpreter and try to import the psi module, it[...]
> fails with the following message.
> >>> import psiThis is simply the python import path that is surprising you. If you
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "psi/__init__.py", line 43, in ?
> from psi._psi import AttrNotAvailableError, AttrInsufficientPrivsError,
> \
> ImportError: No module named _psi
check your sys.path you will notice that the current directory is on
it, and your current directory -the psi toplevel directory- has the
pure-python source of psi inside the psi/ directory. When python
tries to use that it is missing the extension modules.
If you want to try psi without installing it you can just cd into the
build/lib.linux-x86_64-2.6/ (or whatever it is for your system)
directory before starting python.