[Calendarserver-maintainers] Bug#747554: python-vobject: python3 branch

Guido Günther agx at sigxcpu.org
Tue Jan 26 17:44:28 UTC 2016

On Mon, Jan 25, 2016 at 10:03:43PM +0100, chrysn wrote:
> On Mon, Jan 25, 2016 at 03:52:43PM +0100, Petter Reinholdtsen wrote:
> > Any news on a new upstream for vobject?
> as far as i can tell, upstream is inactive; last release was in 2009.
> i've been in contact with jeffrey, he gave his ok to take over the
> project, and offered the existing website to a new location.
> > Perhaps someone would be willing to take over the development of
> > the project?
> i'd be happy to provide bugfixes, but i don't have the overview of the
> complete thing i'd need to take over in full.
> are you more familiar with the scope of which features are used? which
> api guarantees are in place?
> On Mon, Jan 25, 2016 at 07:53:28PM +0100, Guido Günther wrote:
> > It seems radicale now supports python3 as well and I wonder what they
> > use, did you check? Maybe they already maintain a fork?
> as far as i can tell, radicale doesn't fully parse the vobject but just
> understands enough of it to assemble vobjects into collections, on the
> base of line.startswith("UID:") and similar (see [1]). calypso is
> exceptionally strict about vobject contents (bugs in calypso's or other
> programs' serialization cause something like "400 Bad Request"
> refusals), but that is one of the key benefits of calypso i perceive.

Thanks for checking this out. This means we're basically on our own with
vobject when it comes to calypso.

 -- Guido

More information about the Calendarserver-maintainers mailing list