Bug#747554: python-vobject: python3 branch
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
> > 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.
There seems to now be python3-icalendar, but I don't know if it can be a
full replacement for vobject. It seems to work for vdirsyncer and khal.
Enrico
--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini
signature.asc
Description: PGP signature
Bug#747554: python-vobject: python3 branch
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.
Cheers,
-- Guido
Bug#747554: python-vobject: python3 branch
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 rdepends python-vobject python-vobject Reverse Depends: calypso urlwatch tryton-modules-party-vcarddav tryton-modules-calendar-todo tryton-modules-calendar-classification tryton-modules-calendar translate-toolkit qreator python-caldav python-pycarddav gnumed-client gcalcl % -- Happy hacking Petter Reinholdtsen
Bug#747554: [Calendarserver-maintainers] Bug#747554: python-vobject: python3 branch
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 development of > the project? It is used by several Debian packages: > It seems radicale now supports python3 as well and I wonder what they use, did you check? Maybe they already maintain a fork? Cheers, -- Guido
Bug#747554: python-vobject: python3 branch
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.
best regards
chrysn
[1] https://github.com/Kozea/Radicale/blob/master/radicale/ical.py#L66
--
To use raw power is to make yourself infinitely vulnerable to greater powers.
-- Bene Gesserit axiom
signature.asc
Description: PGP signature
Bug#747554: python-vobject: python3 branch
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 deploy my software locally, and therefore I dropped the 0002-Deepcopy-params.patch because it did not apply cleanly and I had no context (like a bug reference) or time to work on it. I also don't know how to package things with python3 and cdbs, so I redid the packaging the way I know: with python-stdeb and debdry. I want to clarify again that this was done for my internal consumption. Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini enr...@enricozini.org debian.tar.xz Description: application/xz signature.asc Description: Digital signature
Bug#747554: python-vobject: python3 branch
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 enjoying your port quite a lot. Hic!
I was sad to read that upstream looks inactive.
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:
commit 74b4fd0a90929ee7b88400e97358b84df13846cb
Author: Enrico Zini enr...@enricozini.org
Date: Mon Dec 22 21:39:00 2014 +0100
Deal with out of range years
diff --git a/vobject/icalendar.py b/vobject/icalendar.py
index ec6079a..f982f5c 100644
--- a/vobject/icalendar.py
+++ b/vobject/icalendar.py
@@ -1606,6 +1606,10 @@ def stringToDateTime(s, tzinfo=None):
tzinfo = utc
except:
raise ParseError('%s' is not a valid DATE-TIME % s)
+if year datetime.MINYEAR:
+year = datetime.MINYEAR
+if year datetime.MAXYEAR:
+year = datetime.MAXYEAR
return datetime.datetime(year, month, day, hour, minute, second, 0, tzinfo)
Enrico
--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini enr...@enricozini.org
signature.asc
Description: Digital signature
Bug#747554: [Calendarserver-maintainers] Bug#747554: python-vobject: python3 branch
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 uploads of a python3-vobject to Debian in case you want to maintain it. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747554: python-vobject: python3 branch
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 and fixing until the unit tests worked. (most of the porting was deciding whether to use str or bytes in a particular situation, following python3 renames like next/__next__ or the quopri module, adapting to the way exceptions are printed and sorting dictionaries where the unit tests relied on undetermined behavior that happened to work consistently in python2). i've stored my changes in a git repository that is based on debian's history of importing upstream tarballs, as the upstream svn seems to have gone away. as the patch history is basically linear, it should be easy to rebase onto an existing better git rendition of the project's history if there is one. it can be fetched with [2]. if there is anybody still maintaining this project, please consider accepting my python3 branch. otherwise, this would be a good occasion for the package users and downstreams to think of whether we want to organize im some way to keep the project alive. best regards chrysn [1] https://bugs.debian.org/747554 [2] git clone git://prometheus.amsuess.com/vobject -b python3 -- Most people would leave. Not us. We're Vikings. We have stubbornness issues. -- Hiccup, son of Stoic signature.asc Description: Digital signature
