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