(I couldn't resist the programmer humor of the subject, but anyway...)
Hi everyone.
I ran up against an issue running unit tests. It turned out to be a bug
with an old version of nose, which was being used instead of the
"official" version unbeknown to me. Thanks to Mary for pointing it
out. I point it out here as it may be helpful to you.
(FYI: The problem was that the unit test framework was not honoring the
PYTHONPATH (which included my proto area) and looking for modules only
in /usr/lib/python2.6/vendor-packages.)
Turns out I was running nose* 0.11.4 which I "easy-installed" a long
time ago (in ...python2.6/site-packages). In order to run the more
current, less buggy version under .../python2.6/vendor-packages, I had
to comment out the nose 0.11.4 entry in:
/usr/lib/python2.6/site-packages/easy-install.pth
*Note: I'm talking about nose, not NoseXUnit.
I also deleted the nose-0.11.4-py2.6.egg directory tree under
site-packages. When I first renamed it (just to be safe), the more
current nose ran regardless of the entry in easy-install.pth. (It must
look under site-packages first, and then fall back to vendor-packages if
the site-packages entry doesn't exist.)
I have filed the following bug for the tools/tests/README to be updated
in slim_source:
7185852 Update tools/tests/README to mention removal of old
easy-installed nose so updated nose runs.
FYI:
strongheart:/usr/lib/python2.6/vendor-packages # pkg list core-os nose
NAME (PUBLISHER)
VERSION IFO
library/python-2/nose
1.1.2-0.175.1.0.0.20.0 i--
system/core-os
0.5.11-0.175.1.0.0.20.0 i--
Thanks,
Jack
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
