On Sun, May 20, 2007 at 07:02:21PM +0300, Martynas Venckus wrote:
> Really? Maybe it does not *need* it; but it does make use of it;
In my opinion, the twisted integration is extra functionality. I
would rather enable it in a FLAVOR or subpackage, though I
understand if you'd prefer to simply leave it in.
> It does not for me.
>
> Using nosetests(1):
>
> $ make regress
> ===> Regression check for py-nose-0.9.3
> cd /usr/obj/ports/py-nose-0.9.3/nose-0.9.3/unit_tests &&
> /usr/local/bin/nosetests
> .....................................................................................................................
> ----------------------------------------------------------------------
> Ran 118 tests in 1.965s
>
> OK
Odd - after fixing the Makefile (I had to change '${LOCALBASE}/nosetests'
to '${LOCALBASE}/bin/nosetests' in do-regress), I get the following
on regress:
===> py-nose-0.9.3 depends on: py-nose-* - found
===> py-nose-0.9.3 depends on: py-twisted-core-* - found
===> Regression check for py-nose-0.9.3
cd /usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3/unit_tests &&
/usr/local/bin/nosetests
----------------------------------------------------------------------
Ran 0 tests in 0.005s
OK
With do-regress commented out, I get:
===> Regression check for py-nose-0.9.3
running test
running egg_info
writing nose.egg-info/PKG-INFO
writing top-level names to nose.egg-info/top_level.txt
writing dependency_links to nose.egg-info/dependency_links.txt
writing entry points to nose.egg-info/entry_points.txt
reading manifest file 'nose.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'unit_tests/*/*/*/*/*.py'
writing manifest file 'nose.egg-info/SOURCES.txt'
running build_ext
collector in ['/usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3'] ...
test module nose in /usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3/lib ...
test directory /usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3/lib/nose in
nose ... test module nose.plugins in
/usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3/lib ... test directory
/usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3/lib/nose/plugins in
nose.plugins ... test module nose in
/usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3 ... test directory
/usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3/nose in nose ... test
module nose.plugins in /usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3 ...
test directory /usr/ports/devel/py-nose/w-py-nose-0.9.3/nose-0.9.3/nose/plugins
in nose.plugins ...
----------------------------------------------------------------------
Ran 9 tests in 0.034s
OK
That's somewhat better, but still not very good. ;) I don't
understand yet why you and I get such different results -- perhaps
you have an updated version of the port available?
At the very least, we can avoid relying on
${LOCALBASE}/bin/nosetests by using one of the methods documented in
nose/__init__.py. I'll see if I can come up with something.
> Using setup.py tests:
The errors you got look like you need to set PYTHONPATH correctly.
--
o--------------------------{ Will Maier }--------------------------o
| web:.......http://www.lfod.us/ | [EMAIL PROTECTED] |
*------------------[ BSD Unix: Live Free or Die ]------------------*
