#44308: py-SRPAstro: switch PIL/Pillow dependency to py-matplotlib and py-scipy. -------------------------------------------------+---------------------- Reporter: ionic@… | Owner: petr@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: haspatch Port: py-SRPAstro py-matplotlib py-scipy | -------------------------------------------------+---------------------- Comment (by ionic@…): `scipy`: {{{ /opt/local/var/macports/build/_opt_macports_python_py- scipy/py26-scipy/work/scipy-0.14.0/scipy/misc/pilutil.py: from PIL import Image, ImageFilter /opt/local/var/macports/build/_opt_macports_python_py- scipy/py26-scipy/work/scipy-0.14.0/scipy/misc/pilutil.py: import Image /opt/local/var/macports/build/_opt_macports_python_py- scipy/py26-scipy/work/scipy-0.14.0/scipy/misc/pilutil.py: import ImageFilter /opt/local/var/macports/build/_opt_macports_python_py- scipy/py26-scipy/work/scipy-0.14.0/scipy/ndimage/io.py: from PIL import Image }}} Yes, `PIL` is an optional dependency for both `scipy` and `matplotlib`, but I think it's highly recommended to have the modules around for having a complete feature set. Maybe adding `PIL`/`Pillow` as a hard dependency is wrong, but it may certainly warrant a variant (to my mind even turned on by default.) `SRPAstro` does formally depend on `PIL`, but only due to `scipy`/`matplotlib`. I haven't checked exactly, but I figure it uses classes from `scipy`/`matplotlib` which are only available with `PIL`. The author confirmed this. -- Ticket URL: <https://trac.macports.org/ticket/44308#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X