nose provides an alternate test discovery and running process for
unittest, one that is intended to mimic the behavior of py.test as
much as is reasonably possible without resorting to magic. By default,
nose will run tests in files or directories under the current working
directory whose names include "test". nose also supports doctest tests
and may optionally provide a test coverage report.
WWW: http://somethingaboutorange.com/mrl/projects/nose/
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
Create new port devel/py3-nose:
- This is a variant of devel/py-nose for Python 3.x.
A separate port is needed until the ports tree gets VARIANTS support.
The science/gramps port will soon be updated to a version which only
supports python3, and it depends on py-nose with python3.
To allow people to only use packages directly (and not ports),
the package building infrastructure needs to build 2 packages:
py-nose with python2 and py-nose with python3.
Since the ports tree doesn't yet have VARIANTS support, this is not
yet possible without making a separate py3-nose port.
- Ensure devel/py-nose does not clobber USES variable in slave devel/py3-nose
- Fix devel/py-nose target regression-test to use selftest.py [1]
[1] https://github.com/nose-devs/nose/issues/400
PR: 207036
Reviewed by: mat (mentor)
Approved by: adamw (mentor), koobs (maintainer)
Differential Revision: https://reviews.freebsd.org/D6280
