Bug#787902: [Python-apps-team] Bug#787902: Bug#787902: pelican: Please provide a python3 module
if pelican module is not used outside the application, please move it to private directory (bonus points for using python3 rather than python) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787902: [Python-apps-team] Bug#787902: pelican: Please provide a python3 module
On Mon, Jun 15, 2015 at 11:54 PM, Johannes Schauer jo...@debian.org wrote: 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? I haven't been keeping up with all the traffic from debian-python lately, but my understanding of the current situation is that python libraries/modules should have both python2 and python3 binary packages whenever possible (or be ported to python 3 if not yet already ported), while python application maintainers are free to choose to use either python2 or python3. IMO for python applications, it makes sense to just depend on whatever python version is currently the default, so that end users (many of who are not necessarily python developers and consider this an implementation detail they don't care about) end up with just a single (default) version of python installed. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787902: [Python-apps-team] Bug#787902: pelican: Please provide a python3 module
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 signature.asc Description: signature
Bug#787902: [Python-apps-team] Bug#787902: pelican: Please provide a python3 module
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
Bug#787902: pelican: Please provide a python3 module
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!
cheers, josch
diff -Nru pelican-3.5.0/debian/changelog pelican-3.5.0/debian/changelog
--- pelican-3.5.0/debian/changelog 2014-11-06 08:56:55.0 +0100
+++ pelican-3.5.0/debian/changelog 2015-06-06 08:12:57.0 +0200
@@ -1,3 +1,10 @@
+pelican (3.5.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * build a python3 module as well
+
+ -- Johannes Schauer jo...@debian.org Sat, 06 Jun 2015 08:12:43 +0200
+
pelican (3.5.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru pelican-3.5.0/debian/control pelican-3.5.0/debian/control
--- pelican-3.5.0/debian/control 2014-11-06 08:57:01.0 +0100
+++ pelican-3.5.0/debian/control 2015-06-06 08:38:25.0 +0200
@@ -5,8 +5,26 @@
Uploaders: Ondřej Surý ond...@debian.org, Vincent Cheng vch...@debian.org
Build-Depends:
debhelper (= 7.4.3),
+ python-setuptools (= 0.6b3),
python-all (= 2.6.6-3),
- python-setuptools (= 0.6b3)
+ python-dateutil,
+ python-unidecode,
+ python-blinker,
+ python-tz,
+ python-docutils,
+ python-pygments,
+ python-jinja2,
+ python-feedgenerator,
+ python3-all,
+ python3-setuptools,
+ python3-dateutil,
+ python3-unidecode,
+ python3-blinker,
+ python3-tz,
+ python3-docutils,
+ python3-pygments,
+ python3-jinja2,
+ python3-feedgenerator,
Standards-Version: 3.9.6
X-Python-Version: = 2.7
Homepage: http://getpelican.com/
@@ -24,7 +42,26 @@
Suggests:
pandoc,
python-bs4
-Description: blog aware, static website generator
+Description: blog aware, static website generator (Python 2 version)
+ Pelican is a static site generator, written in Python. It allows you
+ to write your weblog entries directly with your editor of choice in
+ reStructuredText or Markdown, and generates completely static output
+ that is easy to host anywhere. Pelican includes a simple CLI tool to
+ (re)generate the weblog and it is easy to interface with DVCSes and web
+ hooks.
+
+Package: python3-pelican
+Architecture: all
+Depends:
+ python3-argparse | python (= 2.7),
+ python3-markdown,
+ python3-pkg-resources,
+ ${misc:Depends},
+ ${python3:Depends}
+Suggests:
+ pandoc,
+ python-bs4
+Description: blog aware, static website generator (Python 3 version)
Pelican is a static site generator, written in Python. It allows you
to write your weblog entries directly with your editor of choice in
reStructuredText or Markdown, and generates completely static output
diff -Nru pelican-3.5.0/debian/pydist-overrides pelican-3.5.0/debian/pydist-overrides
--- pelican-3.5.0/debian/pydist-overrides 2014-08-04 10:37:42.0 +0200
+++ pelican-3.5.0/debian/pydist-overrides 1970-01-01 01:00:00.0 +0100
@@ -1,7 +0,0 @@
-feedgenerator python-feedgenerator
-jinja2 python-jinja2
-pygments python-pygments
-docutils python-docutils
-blinker python-blinker
-unidecode python-unidecode
-six python-six
diff -Nru pelican-3.5.0/debian/python3-pelican.install pelican-3.5.0/debian/python3-pelican.install
--- pelican-3.5.0/debian/python3-pelican.install 1970-01-01 01:00:00.0 +0100
+++ pelican-3.5.0/debian/python3-pelican.install 2015-06-06 08:12:39.0 +0200
@@ -0,0 +1 @@
+usr/lib/python3*
diff -Nru pelican-3.5.0/debian/python-pelican.install pelican-3.5.0/debian/python-pelican.install
--- pelican-3.5.0/debian/python-pelican.install 1970-01-01 01:00:00.0 +0100
+++ pelican-3.5.0/debian/python-pelican.install 2015-06-06 08:12:32.0 +0200
@@ -0,0 +1 @@
+usr/lib/python2*
diff -Nru pelican-3.5.0/debian/rules pelican-3.5.0/debian/rules
--- pelican-3.5.0/debian/rules 2014-08-04 10:37:42.0 +0200
+++ pelican-3.5.0/debian/rules 2015-06-06 08:38:08.0 +0200
@@ -1,12 +1,18 @@
#!/usr/bin/make -f
%:
- dh $@ --with python2 --buildsystem=python_distutils
+ dh $@ --with python2,python3 --buildsystem=pybuild
override_dh_clean:
dh_clean
rm -f pelican.egg-info/SOURCES.txt pelican.egg-info/requires.txt
+# the test suite does not run out of the box because it cannot find the
+# test_generators module in pelican/tests
+# but even after fixing that, there are test cases that do not finish
+# successfully
+override_dh_auto_test:
+
override_dh_installchangelogs:
dh_installchangelogs docs/changelog.rst
