[Python-apps-team] Bug#787902: Bug#787902: pelican: Please provide a python3 module

[Johannes Schauer]

Hi,

Quoting Vincent Cheng (2015-06-16 07:18:24)
> 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.

I'm neither very familiar with Python packaging nor with the plan to transition
from Python2 to Python3, but naively I would've thought that when the change of
the default Python version happens would also depend on the number of packages
that do not anymore depend on Python2, no? So would any such transition in the
future not be made easier or earlier if the number of Packages that still
(Build-)Depend on Python2 would be lower? Sure, pelican is just one small
package among thousands so what an impact can it make? But, again naively, I
would've thought that if every tiny package pushes its transition from 2 to 3
into the future, then together they will lead to the switch of the default
version from 2 to 3 being later than earlier. You say that it would not make
much sense to offer both versions at the same time and that is a valid
argument. But what stops src:pelican from just offering the Python 3 version in
a "pelican" binary package now?

In any case, these are just my own 2 cents and of course it is completely up to
you :)

Thanks for maintaining pelican in Debian!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20150616/40cda8e4/attachment.sig>