Migration from python-central to python-support

Hello, since I have read [0], I'm migrating to python-support for the new version of my python-shapely package. But I admit that in the followups of the said mail, I got somehow confused... the 3 lines that Piotr suggests to add: | if [ "$1" = upgrade ] && dpkg --compare-versions "$2" lt 1.2.3-4;

Re: Migration from python-central to python-support

[Pietro Battiston, 2009-05-29] > since I have read [0], I'm migrating to python-support for the new > version of my python-shapely package. > But I admit that in the followups of the said mail, I got somehow > confused... the 3 lines that Piotr suggests to add: > > | if [ "$1" = upgrade ] && dpkg

Bug#531038: ITP: python-repoze-tm2 -- Zope-like transaction manager via WSGI middleware

Package: wnpp Severity: wishlist Owner: Stefano Zacchiroli * Package name: python-repoze-tm2 Version : 1.0a4 Upstream Author : Agendaless Consulting * URL : http://pypi.python.org/pypi/repoze.tm2/ * License : BSD-derived (http://www.repoze.org/LICENSE.txt) P

Bug#531042: ITP: python-toscawidgets -- Web widget creation toolkit based on TurboGears widgets

Package: wnpp Severity: wishlist Owner: Stefano Zacchiroli * Package name: python-toscawidgets Version : 0.9.4 Upstream Author : Alberto Valverde Gonzalez * URL : http://toscawidgets.org/ * License : MIT/X Programming Lang: Python Description : Web wid

Bug#531044: ITP: python-webflash -- Portable flash messages for Python WSGI apps

Package: wnpp Severity: wishlist Owner: Stefano Zacchiroli * Package name: python-webflash Version : 0.1a9 Upstream Author : Alberto Valverde Gonzalez * URL : http://python-rum.org/wiki/WebFlash * License : MIT/X Programming Lang: Python Description :

Bug#531045: ITP: python-repoze-what -- Authorization framework for Python WSGI applications

Package: wnpp Severity: wishlist Owner: Stefano Zacchiroli * Package name: python-repoze-what Version : 1.0.8 Upstream Author : Gustavo Narea * URL : http://www.repoze.org/ * License : BSD-derived (http://www.repoze.org/LICENSE.txt) Programming Lang: Python

Bug#531046: ITP: python-repoze-what-pylons -- Authorization framework for Python WSGI applications - Pylons/TG2 plugin

Package: wnpp Severity: wishlist Owner: Stefano Zacchiroli * Package name: python-repoze-what-pylons Version : 1.0 Upstream Author : Gustavo Narea * URL : http://pypi.python.org/pypi/repoze.what-pylons/ * License : BSD-derived (http://www.repoze.org/LICENSE.tx

pkg-turbogears dead?

Hi Kov and Bob, in the process of packaging Python modules that are needed for TurboGears 2, I've stumbled upon the pkg-turbogears alioth project [1], which looks like dead: not even turbogears 1 dependencies are there and is inactive since 2006. Can you confirm that? Also, it looks like nowada

Packaging plugins for Python applications

Hello, What is the correct umbrella to package a plugin for a Python application under? DPMT or PAPT? And, is there some recommended binary package naming scheme for such packages? I am asking those questions, because I intend[1] to package hg-git[2], a plugin for Mercurial (maintained by P

Bug#531083: ITP: python-repoze.who -- Identification and authentication framework for Python WSGI applications

Package: wnpp Severity: wishlist Owner: Stefano Zacchiroli * Package name: python-repoze.who Version : 1.0.13 Upstream Author : Agendaless Consulting * URL : http://www.repoze.org/ * License : BSD-derived (http://www.repoze.org/LICENSE.txt) Programming Lang:

Re: Packaging plugins for Python applications

Jakub Wilk escribió: > Hello, Hi Jakub, > What is the correct umbrella to package a plugin for a Python > application under? DPMT or PAPT? PAPT, since it's not a module > And, is there some recommended binary package naming scheme for such > packages? Nope, there's only one for modules, but th

Re: Packaging plugins for Python applications

Emilio Pozuelo Monfort writes: > Jakub Wilk escribió: > > What is the correct umbrella to package a plugin for a Python > > application under? DPMT or PAPT? > > PAPT, since it's not a module Hmm? I can't see a reasonable way to package a Python application plug-in that *isn't* a module (or a Py