Debian Patches
Status for python-dicompylercore/0.5.6-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| adjust-collections.patch | fix test failure caused by evolution in collections module. This change addresses the following test failure: . ERROR: test_image_generation (tests.test_dicomparser.TestImage.test_image_generation) Test if the image can be generated. ---------------------------------------------------------------------- Traceback (most recent call last): File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/tests/test_dicomparser.py", line 141, in test_image_generation self.assertEqual(self.dp.GetImage().getpixel((255, 254)), image) ~~~~~~~~~~~~~~~~^^ File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/dicompylercore/dicomparser.py", line 407, in GetImage image = self.GetLUTValue(rescaled_image, window, level) File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/dicompylercore/dicomparser.py", line 472, in GetLUTValue lutvalue = util.piecewise( data, ...<3 lines>... ((data - (level - 0.5)) / (window-1) + 0.5) * (255 - 0)]) File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/dicompylercore/util.py", line 135, in piecewise if not isinstance(item, collections.Callable): ^^^^^^^^^^^^^^^^^^^^ AttributeError: module 'collections' has no attribute 'Callable' |
Étienne Mollier <emollier@debian.org> | no | debian | 2025-02-16 | |
| remove-six.patch | [PATCH] Remove Python 2 support (#367) * Removed Python 2 support. * Updated documentation to indicate removal of Python 2 support. |
Aditya Panchal <apanchal@bastula.org> | no | 2023-06-12 | ||
| skip-tight-comparison.patch | skip tight comparison failing with numpy 2.x. This patch works around the following test failure: . FAIL: test_raw_data_dvh (tests.test_dvh.TestDVH.test_raw_data_dvh) Test if a DVH can be created from raw data. ---------------------------------------------------------------------- Traceback (most recent call last): File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/tests/test_dvh.py", line 41, in test_raw_data_dvh self.assertEqual( ~~~~~~~~~~~~~~~~^ repr(dvh.DVH.from_data(1, 1)), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "DVH(cumulative, 1 bins: [0:1] Gy, volume: 1 cm3, " ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "name: None, rx_dose: 0 Gy)") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError: 'DVH([16 chars]ns: [np.int64(0):np.int64(1)] Gy, volume: np.i[35 chars] Gy)' != 'DVH([16 chars]ns: [0:1] Gy, volume: 1 cm3, name: None, rx_dose: 0 Gy)' - DVH(cumulative, 1 bins: [np.int64(0):np.int64(1)] Gy, volume: np.int64(1) cm3, name: None, rx_dose: 0 Gy) ? --------- - --------- - --------- - + DVH(cumulative, 1 bins: [0:1] Gy, volume: 1 cm3, name: None, rx_dose: 0 Gy) . The end result of the computation is no different from the normal result, so it is okay to skip it. The main issue looks to be that with newer numpy versions, the check becomes too restrictive with its expectation of how types ought to be formatted. |
Étienne Mollier <emollier@debian.org> | not-needed | debian | 2025-02-16 |
Showing 1 to 3 of 3 entries