| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-removes_external_images_from_readme_rst.patch | removes_external_images_from_readme_rst | Boyuan Yang <byang@debian.org> | no | 2022-07-24 | ||
| 0002-Recover-nose2._version.__version__.patch | Recover nose2._version.__version__ Needed for sphinx build. |
Boyuan Yang <byang@debian.org> | no | 2022-07-24 | ||
| 0003-Avoid-setuptools-PackageDiscoveryError.patch | Avoid setuptools PackageDiscoveryError Otherwise the following error message happens: setuptools.errors.PackageDiscoveryError: Multiple top-level packages discovered in a flat-layout: ['nose2', 'debian']. To avoid accidental inclusion of unwanted files or directories, setuptools will not proceed with this build. If you are trying to create a single distribution with multiple packages on purpose, you should not rely on automatic discovery. Instead, consider the following options: 1. set up custom discovery (`find` directive with `include` or `exclude`) 2. use a `src-layout` 3. explicitly set `py_modules` or `packages` with a list of names To find more information, look for "package discovery" on setuptools docs. |
Boyuan Yang <byang@debian.org> | no | 2023-07-23 | ||
| 0004-Python3.12.patch | [PATCH 1/2] Fix verbose reporting of skipped tests On 3.12.1+, unittest doesn't call `startTest` for skipped tests. This is treated as a fix to how tests are counted, which is why it appeared in a point release. Because the nose2 path for test reporting uses the test result methods as the point of connection between `unittest` and nose2 plugins, losing the `startTest` call in this case means that the reporter plugin doesn't emit proper output. The test result object now tracks whether or not a test has been started, and the reporter will check this attribute to ensure that the skipped test output is correct. |
Stephen Rosen <sirosen@globus.org> | yes | 2023-12-21 |