14
0
forked from pool/python-nose2

Accepting request 506615 from home:jengelh:branches:devel:languages:python

let's try this instead

OBS-URL: https://build.opensuse.org/request/show/506615
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-nose2?expand=0&rev=3
This commit is contained in:
2017-06-30 00:32:52 +00:00
committed by Git OBS Bridge
parent e9d001d638
commit b1a92d4bdb
2 changed files with 14 additions and 22 deletions

View File

@@ -1,3 +1,8 @@
-------------------------------------------------------------------
Wed Jun 28 06:07:30 UTC 2017 - jengelh@inai.de
- Update package description
-------------------------------------------------------------------
Mon Apr 24 09:10:11 UTC 2017 - alarrosa@suse.com
@@ -7,4 +12,3 @@ Mon Apr 24 09:10:11 UTC 2017 - alarrosa@suse.com
Mon Feb 6 17:07:51 UTC 2017 - alarrosa@suse.com
- Initial release

View File

@@ -41,25 +41,13 @@ BuildArch: noarch
%python_subpackages
%description
nose2 is the next generation of nicer testing for Python, based
on the plugins branch of unittest2. nose2 aims to improve on nose by:
* providing a better plugin api
* being easier for users to configure
* simplifying internal interfaces and processes
* supporting Python 2 and 3 from the same codebase, without translation
* encouraging greater community involvement in its development
In service of some those goals, some features of nose *will not* be
supported in nose2. See `differences`_ for a thorough rundown.
In time -- once unittest2 supports plugins -- nose2 should be able to
become just a collection of plugins and configuration defaults. For
now, it provides a plugin api similar to the one in the unittest2
plugins branch, and overrides various unittest2 objects.
You are witnesses at the new birth of nose, mark 2. Hope you enjoy our
new direction!
nose2 is a new version of the nose unit testing framework,
supporting Python 2.6+ and 3.x, but not 2.4.
nose2 does not need a custom importer anymore and instead imports
modules with __import__. nose2 does not support all of the
test project layouts that nose did, and also does not
support package-level fixtures. Almost all configuration for nose2
is to be done through config files, not command-line options.
%prep
%setup -q -n nose2-%{version}