[Debian-med-packaging] Bug#985891: [bastula/dicompyler] Please do not use private module matplotlib._cntr (#137)
Andreas Tille
andreas at fam-tille.de
Sat Apr 10 06:20:03 BST 2021
Hi Aditya,
On Fri, Apr 09, 2021 at 08:18:15PM -0700, Aditya Panchal wrote:
> Hope you are doing well. It is possible to use the `legacycontour` package available here: https://github.com/matplotlib/legacycontour and follow the instructions by Alan listed here: https://github.com/bastula/dicompyler/issues/122. That should at least allow the program to function correctly with `matplotlib >= 2.2`.
This will not the problem for the Debian package. The module `legacycontour` is not (yet) packaged for Debian and since we are in freeze currently no new packages are permitted.
> Another option that is possible is to swap to `measure_contours` from `scikit-image` as outlined here: https://github.com/bastula/dicompyler/issues/122#issuecomment-570842862 but introduces a much heavier dependency. One of the goals of dicompyler is to be lightweight.
I admit I have no idea about the goals and features of dicompyler. I'm not using it and simply took over the maintenance in Debian from some developer who left the team to salvage it for the users of the Debian package. So if you can provide a working patch I will include it in the Debian package which will safe it for the next stable release - otherwise it will be removed from there which would be a shame.
Kind regards, Andreas.
More information about the Debian-med-packaging
mailing list