Linux workstation

Upstream software project

nose2

The successor to the Python testing framework nose, based on unittest

About nose2

The successor to the Python testing framework nose, based on unittest

This project links 9 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

nose2 repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 2 package records; Debian 13 (Trixie): 2 package records; openSUSE Leap 15.6: 2 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.nose2: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)2 recordsopenSUSE Leap 15.62 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
nose2
Publisher
Not authoritatively mapped
Native package records
9
Operating systems
debian-12, debian-13, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
BSD-2-Clause AND Python-2.0
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

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.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. python3-nose2

    Debian 12 (Bookworm) / python / source nose2

    0.12.0-1

    Next generation of nicer testing for Python3

    allbookworm
  2. python-nose2-doc

    Debian 12 (Bookworm) / doc / source nose2

    0.12.0-1

    Next generation of nicer testing for Python2/3 (documentation)

    allbookworm

Debian 13 (Trixie)

  1. python3-nose2

    Debian 13 (Trixie) / python / source nose2

    0.15.1-1

    Next generation of nicer testing for Python3

    alltrixie
  2. python-nose2-doc

    Debian 13 (Trixie) / doc / source nose2

    0.15.1-1

    Next generation of nicer testing for Python2/3 (documentation)

    alltrixie

openSUSE Leap 15.6

  1. python311-nose2

    openSUSE Leap 15.6 / Unspecified / source python-nose2

    0.12.0-150400.10.3.9

    The successor to the Python testing framework nose, based on unittest

    noarchleap-15.6
  2. python3-nose2

    openSUSE Leap 15.6 / Development/Languages/Python / source python-nose2

    0.9.1-3.3.4

    Second generation of the "nose" Python testing framework

    noarchleap-15.6

openSUSE Leap 16.0

  1. python313-nose2

    openSUSE Leap 16.0 / Unspecified / source python-nose2

    0.15.1-160000.2.2

    The successor to the Python testing framework nose, based on unittest

    noarchleap-16.0

openSUSE Tumbleweed

  1. python313-nose2

    openSUSE Tumbleweed / Unspecified / source python-nose2

    0.16.0-1.3

    The successor to the Python testing framework nose, based on unittest

    noarchtumbleweed
  2. python314-nose2

    openSUSE Tumbleweed / Unspecified / source python-nose2

    0.16.0-1.3

    The successor to the Python testing framework nose, based on unittest

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.