2014-07-21 10:59 GMT+02:00 Christopher Meng <cickumqt(a)gmail.com>:
I just want to ask here, why did you retire the pywcs and considered
it as dead upstream whereas pypi pywcs has a new release in the
The functionallity of pywcs is now in astropy, is where active development
is happening. The API is the same. Sometimes the developers backport the
code to pywcs, but is a dead end.
And now APLpy is broken.
I contacted the maintainer before the change and he agreed to update to
APLpy 0.9.11 that uses astropy instead of pywcs. He hasn't updated yet.
In this report there is a new specfile for APLpy 0.9.11. I would have
updated myself but I'm not a proven packager.