On Sat, Jun 6, 2015 at 12:03 AM, Johannes Schauer <jo...@debian.org> wrote: > Source: pelican > Version: 3.5.0-1 > Severity: wishlist > Tags: patch > > Control: block -1 by 787897 > > Hi, > > I noticed that pelican still relies on Python 2 even though upstream > supports Python 3. > > The attached patch rectifies the situation. > > The patch can only be applied once feedgenerator offers a Python 3 > module (bug #787897). > > While changing the dh --buildsystem to pybuild, I tried getting the test > suite to work but ran into several problems. Thus I deactivated running > the test suite for now.
Thanks for the patch! However, as pelican is intended to be used more as an application (it's a static site generator), rather than a set of standalone python modules, I don't think it particularly makes sense to offer both a python2 and python3 version of pelican. I'm inclined to just build src:pelican using whatever is the default version of python in Debian, and eventually rename the binary python-pelican package to just pelican. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org