Best practice for adding python3 version to existing module with helper programs?
I'm working on packaging the latest version of sqlobject, which adds supprt for python 3, and I'm unsure of how best to handle the helper applications that ship as part of the package. The helper applications will work with both python2 and python3, so it's not clear to me how to apply the advice given in [1], and I'd ideally want the helper programs available regardless of which version of the module is installed. Looking at some other packages in the archive, there seem to be several approaches used to solve similar problems a) Bundle the application in both python2 and python3 version and use alternatives to manage the version (docutils and sphinx, for example, although in those cases the programs are used fairly extensively as applications) b) Install multiple copies with different names (foo and foo-py3 and similar ideas) c) Replace the helper with a combination shell / python script (django-admin for example [2]), which is cute. Is there any consensus on which approach is best? Any advice on the pitfalls or benefits of the various approachs? Other tricks I've missed? Thanks [1] https://wiki.debian.org/Python/LibraryStyleGuide [2] https://anonscm.debian.org/cgit/python-modules/packages/python-django.git/tree/debian/django-admin -- Neil Muller
Request to join PAPT
I sent a request to join the PAPT via alioth [1] some weeks ago, but there doesn't appear to have been any response to that. I intend to adopt irker [2], and would like to see it maintained as part of the PAPT. My alioth username is drnlmza-guest . I am already a member of the DPMT [3]. Thanks [1] As is currently specified by http://python-apps.alioth.debian.org/policy.html [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756090 [3] Currently taking care of sqlobject & pydispatcher .
Taking over SQLObject package?
The current python-sqlobject package is decidedly outdated (SQLObject upstream is at 1.4, released this konth while debian is still at 0.12.4, released in 2010), and the last 2 uploads (in 2012 and 2013) have been NMUs. As a reasonably heavy user of SQLObject, find this state a considerable annoyance. Since I'm responsible for the last NMU, and have a decent relationship with upstream, would anyone object to me taking over the debian package? -- Neil Muller -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capzz3haqonvnwkj7ff6kbm6w7gp-sjuqgbpsa0-zrf5ss_v...@mail.gmail.com
