Package: nosy
IntroductionRun thenosetest discovery and execution tool whenever a source file
is changed.An elaborated version of Jeff Winkler’snosytool that runs nose
whenever a source file is changed.  This version has a command line
parser added, and the capability to use a configuration file to
control what files are watched, and how nose runs.Synopsis$ nosy -hUsage: nosy [options]Automatically run nose whenever source files change.Options:-h,--helpshow this help message and exit-cCONFIG_FILE,--config=CONFIG_FILEconfiguration file path and name; defaults to
setup.cfgConfiguration FileConfiguration file section contents example:[nosy]
# Paths to check for changed files; changes cause nose to be run
base_path = ./
glob_patterns = *.py
exclude_patterns = *_flymake.*
extra_paths = sample.cfg
# Command line options to pass to nose
options = -x
# Command line arguments to pass to nose; e.g. part of test suite to run
tests = tests/unit_tests.pyConfiguration file is read by a Python standard library ConfigParser
object, so:Lines beginning with “#” or “;” are ignored and may be used to
provide comments.Entries can be in the form “name: value” or “name=value”, with
continuations in the style of RFC 822.Leading whitespace is removed from values.Format string substitution in values is supported.Within the[nosy]section 6 options may be specified:base_path- The directory in which to start walking the tree to
check for changed files. Defaults to..glob_patterns- A whitespace separated list of shell glob
patterns to check for changes. Defaults to*.py.exclude_patterns- A whitespace separated list of shell glob
patterns to exclude when checking for changes. Defaults to‘’.extra_paths- A whitespace separated list of shell glob patterns
to add to the paths that are checked for changes. Defaults to‘’.options- A string of options to be passed through to nose when
it is executed.tests- A string of command line arguments to be passed through
to nose when it is executed.  Useful for specifying part of the
test suite to run.Including the configuration file in the watched paths allows you to
change nose’s behaviour on the fly.The source code and bug tracker for this package is available onBitbucket.Changelogv1.2 6-Dec-2015Change exception handling to preserve backward compatibility with
Python 2.5.Add Vagrant and tox configurations for automation of testing against
multiple Python versions.Add support for Python 3.2, 3.3, 3.4, and 3.5.
Thanks to@ronnixand@StefanWiechulafor pull requests,
and to@jacebrowningfor in-use testing.Fix test suite issues re: multiple Python versions.Addtest_runneroption in the config file to specify the test
runner command to use; defaults tonosetests.v1.1.2 15-Sep-2011Fix packaging errors. CHANGELOG was missing from MANIFEST.in, and
setup.py failed under Python 2.5 due to the use of context managers.v1.1.1 13-Sep-2011Refactored checksum calculations to flatten nested loops and improve
testability.Added test suite.Fixed a bug that causednosenot to run whenexclude_patternswas empty. Thanks to Greg Haskins for the
patch, and an anonymous issue reporter on Bitbucket.Fixed a bug that caused files in thebase_pathnot to be
monitored. Thanks to Greg Haskins for the patch.v1.1 21-Mar-2011Configuration file now defaults tosetup.cfg.New configuration options to make it easier to usenosyin
projects with deep directory structures. The checksum calculator now
usesos.walk()starting frombase_path, including files
given by a list ofglob_patterns, excluding those given by a
list ofexclude_patterns. Files given by theextra_pathslist are also glob-ed in to handle anything that the first 3 options
don’t easily catch. Thanks to Jussi Rasinmäki for the suggestion.Thepathsconfiguration option is retained for backward
compatibility only.Changed fromsetuptoolstodistributefor packaging.Source code and issue tracker now on bitbucket.org:https://bitbucket.org/douglatornell/nosyReleased under New BSD License.Released on PyPI:http://pypi.python.org/pypi/nosyv1.0 13-Jun-2008Original release.