Bug#747554: python-vobject: python3 branch

2016-05-15 Thread Enrico Zini
On Tue, Jan 26, 2016 at 06:44:28PM +0100, Guido Günther wrote: > > 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 > >

Bug#747554: python-vobject: python3 branch

2016-01-26 Thread Guido Günther
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

Bug#747554: python-vobject: python3 branch

2016-01-25 Thread Petter Reinholdtsen
I just tried porting calypso to python3 (do not seem very hard), but one of the blockers is the lack of python3-vobject. Any news on a new upstream for vobject? Perhaps someone would be willing to take over the development of the project? It is used by several Debian packages: % apt-cache

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

2016-01-25 Thread Guido Günther
Hi, On Mon, Jan 25, 2016 at 03:52:43PM +0100, Petter Reinholdtsen wrote: > I just tried porting calypso to python3 (do not seem very hard), but > one of the blockers is the lack of python3-vobject. Any news on a > new upstream for vobject? > > Perhaps someone would be willing to take over the

Bug#747554: python-vobject: python3 branch

2016-01-25 Thread chrysn
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

Bug#747554: python-vobject: python3 branch

2014-12-23 Thread Enrico Zini
On Mon, Dec 22, 2014 at 09:41:57PM +0100, Enrico Zini wrote: I have added this patch on top of your work, as porting somehow dropped that check, and I stumbled on an .ics feed with a broken year: I'm attaching my debian/ directory for python3 packaging. I did it as emergency work so I could

Bug#747554: python-vobject: python3 branch

2014-12-22 Thread Enrico Zini
On Fri, Sep 12, 2014 at 06:07:14PM +0200, chrysn wrote: following my bug report on [1], i have ported vobject to python3, it now passes all the unit tests (on which it was attempted to keep chanes minimal). Hello, thanks for porting vobject to python3: I also have a need for it, and I'm

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

2014-09-14 Thread Guido Günther
On Fri, Sep 12, 2014 at 06:07:14PM +0200, chrysn wrote: hello vobject developers, users and packagers, following my bug report on [1], i have ported vobject to python3, it now passes all the unit tests (on which it was attempted to keep chanes minimal). Awesome. I'd be happy to sponsor

Bug#747554: python-vobject: python3 branch

2014-09-12 Thread chrysn
hello vobject developers, users and packagers, following my bug report on [1], i have ported vobject to python3, it now passes all the unit tests (on which it was attempted to keep chanes minimal). the port does not try to be dual-version -- it works on python3 only, based on an initial 2to3 run