PYTHON-680 Remove all references to nose
This commit is contained in:
parent
141200083e
commit
327fdaa560
1
.gitignore
vendored
1
.gitignore
vendored
@ -11,6 +11,5 @@ dist/
|
||||
tools/settings.py
|
||||
pymongo.egg-info/
|
||||
*.so
|
||||
nosetests.xml
|
||||
*.egg
|
||||
.tox
|
||||
|
||||
10
README.rst
10
README.rst
@ -64,7 +64,7 @@ support Python 2.4, 2.5, and 3.1.
|
||||
Additional dependencies are:
|
||||
|
||||
- (to generate documentation) sphinx_
|
||||
- (to auto-discover tests) `nose <http://somethingaboutorange.com/mrl/projects/nose/>`_
|
||||
- (to run the tests under Python 2.6) unittest2_
|
||||
|
||||
Examples
|
||||
========
|
||||
@ -115,9 +115,9 @@ setup.py doc**. Generated documentation can be found in the
|
||||
Testing
|
||||
=======
|
||||
|
||||
The easiest way to run the tests is to install `nose
|
||||
<http://somethingaboutorange.com/mrl/projects/nose/>`_ (**easy_install
|
||||
nose**) and run **nosetests** or **python setup.py test** in the root
|
||||
of the distribution. Tests are located in the *test/* directory.
|
||||
The easiest way to run the tests is to run **python setup.py test** in
|
||||
the root of the distribution. Note that you will need unittest2_ to
|
||||
run the tests under Python 2.6.
|
||||
|
||||
.. _sphinx: http://sphinx.pocoo.org/
|
||||
.. _unittest2: https://pypi.python.org/pypi/unittest2
|
||||
|
||||
13
RELEASE.rst
13
RELEASE.rst
@ -32,12 +32,13 @@ Doing a Release
|
||||
with and without the C extension. Generally enough to just run the tests on
|
||||
2.6, 2.7, 3.2 and the latest 3.x version with and without the extension on
|
||||
a single platform, and then just test any version on the other platforms
|
||||
as a sanity check. `python setup.py test` will build the extension and test.
|
||||
`python tools/clean.py` will remove the extension, and then `nosetests` will
|
||||
run the tests without it. Run the replica set and mongos high-availability
|
||||
tests with `PYTHONPATH=. python test/high_availability/test_ha.py` and the slow
|
||||
tests with `nosetests -d test/slow`. Can also run the doctests: `python
|
||||
setup.py doc -t`. For building extensions on Windows check section below.
|
||||
as a sanity check. `python setup.py test` will build the extension
|
||||
and test. `python tools/clean.py` will remove the extension, and
|
||||
then `python setup.py --no_ext test` will run the tests without
|
||||
it. Run the replica set and mongos high-availability tests with
|
||||
`PYTHONPATH=. python test/high_availability/test_ha.py`. Can also
|
||||
run the doctests: `python setup.py doc -t`. For building extensions
|
||||
on Windows check section below.
|
||||
|
||||
2. Add release notes to doc/changelog.rst. Generally just summarize/clarify
|
||||
the git log, but might add some more long form notes for big changes.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user