I followed up on this with calendarserver upstream. The only feasible
solution seems to be rolling out a new compatible python-sqlparse
package separately for calendarserver. I don't know think new packages
are accepted now in stretch. Moreoever, I don't want to go through all
this hassle as the next calendarserver release would probably take care
of sqlparse 0.2.x compatibility.
So, I have decided to backport calendarserver 5.x or 7.x to
jessie-backports for now. Few months later, when the newer
calendarserver compatible with sqlparse 0.2.x is released, I will
backport it to stretch-backports.
Thanks,
Rahul.
--
http://rahul.amaram.name
