pynose
pynose fixes nose to extend unittest and make testing easier
Decision gist · record as of 2026-08-14
Yes. pynose is worth installing if you have an existing test suite or prefer its discovery and output-capture model. It is actively maintained, has no runtime dependencies, installs easily, and fixes all known compatibility issues with modern Python. The copyleft license (GNU LGPL) is not a barrier for most open-source projects but should be reviewed by proprietary teams. No known vulnerabilities.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.7 or later.
- Low install friction with no runtime dependencies.
- Actively maintained as of 2026-06-01 with recent releases; compatible with Python 3.7 through 3.14.
License · maintenance · safety
GNU LGPL (copyleft) — Licensed under GNU LGPL (copyleft). Any derivative work or modification must be distributed under the same or compatible copyleft license; proprietary projects should review copyleft obligations before use.
last release 2025-09-08 (340 days) · last repo commit 2026-06-01 · 16 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 1,080,380 downloads/mo, #4,396 on PyPI
Alternatives
Verify before relying
pip install pynose
# Run tests in current directory
pynose
# Or use the nosetests command
nosetests [options] [test files or directories]
# Or import in a script
import pynose- Whether the package maintains full backward compatibility with plugins written for the original nose.
- Performance characteristics compared to other test discovery tools for large test suites.
- Specific details on which plugins are included or supported by default.
What it is and what it does
pynose is a maintained fork that extends unittest with automatic test discovery and flexible test selection. It fixes multiple compatibility issues that broke the original version under modern Python—including AttributeError from deprecated collections.Callable and inspect.getargspec, ImportError from unittest internals, and deprecation warnings from pkg_resources. The package replaces the obsolete imp module with importlib and adds features like --capture-logs, --logging-init, and --capture-output for controlling test output verbosity.
Developers use pynose to run tests via command-line tools, which automatically discover test files and functions matching naming patterns, run them with unittest semantics, and capture stdout and logging output from failing tests for debugging. Configuration can be set via command-line flags, .noserc files, or setup.cfg. The package supports plugins for doctest, code coverage, and profiling, and runs on Python 3.7 through 3.14 across Windows, macOS, and Linux.
Use it for
- Migrate legacy test suites to modern Python without rewriting tests or switching frameworks.
- Run tests with automatic discovery and flexible selection by file, module, or test case name.
- Debug failing tests by capturing and displaying print() output and log messages alongside failures.
- Configure test behavior via .noserc or setup.cfg files instead of repeating command-line options.
- Use doctest, coverage, or profiling plugins to extend test capabilities without modifying test code.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
pynose is worth installing if you have an existing test suite or prefer its discovery and output-capture model. It is actively maintained, has no runtime dependencies, installs easily, and fixes all known compatibility issues with modern Python. The copyleft license (GNU LGPL) is not a barrier for most open-source projects but should be reviewed by proprietary teams. No known vulnerabilities.
Install
pynose on PyPI
Before you install
Low install friction with no runtime dependencies. Actively maintained as of 2026-06-01 with recent releases; compatible with Python 3.7 through 3.14.
Requires Python 3.7 or later.
License in practice
Licensed under GNU LGPL (copyleft). Any derivative work or modification must be distributed under the same or compatible copyleft license; proprietary projects should review copyleft obligations before use.
Quickstart
pip install pynose
# Run tests in current directory
pynose
# Or use the nosetests command
nosetests [options] [test files or directories]
# Or import in a script
import pynoseVerify before relying
- Whether the package maintains full backward compatibility with plugins written for the original nose.
- Performance characteristics compared to other test discovery tools for large test suites.
- Specific details on which plugins are included or supported by default.
Package facts
| License | GNU LGPL copyleft |
| Python support | Supports the current Python release >=3.7 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 340 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 1,080,380 / month, #4,396 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableEnvironment :: ConsoleEnvironment :: MacOS XEnvironment :: Win32 (MS Windows)Intended Audience :: DevelopersLicense :: OSI Approved :: GNU Library or Lesser General Public License (LGPL)Natural Language :: EnglishOperating System :: OS IndependentProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9Topic :: Software Development :: Testing |
Evidence: pynose-1.5.5-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “automatic test collection”
- pynosepynose is an updated test runner that extends unittest with automatic…
- nose-py3nose-py3 extends unittest with automatic test discovery and…
- pyats.easypyEasypy is a launcher and runtime environment for pyATS test suites…
Give your agent the search over MCP, or paste the wish link into any chat.
More Testing packages
Pluggy provides a plugin system that lets you define hook specifications and register implementations to be called in sequence, enabling extensible Python applications without tight coupling.
Install it if you're building an extensible application or framework.
pytest is a testing framework that lets you write test functions using plain assert statements and automatically discovers and runs them, with detailed failure reporting.
virtualenv creates isolated Python environments where packages can be installed independently without affecting the system Python or other projects.
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
pytest-asyncio is a pytest plugin that enables writing and running async test functions using the asyncio library, allowing developers to await code directly within test cases.
Install it if you write tests for any asyncio-based code.
A pytest plugin that generates test reports in Common Test Report Format (CTRF) as JSON, compatible with pytest-xdist and pytest-playwright for distributed and browser-based testing.
Install it if you need CTRF-formatted test output for CI/CD integration or cross-tool reporting.
See also nose · nose-py3 · nose2 · django-nose · snapshottest · testscenarios · nosexcover · parameterized · html-testRunner · tap.py