Comment 6 for bug 912625

I might take a look at c2esp, foo2zjs and pyppd in due time.

So far I'm not sure this bug is as uncontroversial as it might seem and would really prefer a discussion about it on <email address hidden> before rushing out any actions. The Debian Python Policy currently says "Maintainers _should_ not use env ..": this doesn't mean it's (currently) forbidden; this even means it discouraged, but allowed.

I don't think creating a Ubuntu-specific diff for this type of bug is the way to go: either there is a valid reason to do it and it should be done in Debian first (with appropriate Debian Python Policy change, lintian warning, etc) or there is none and, well, the cost of the diff will have to be carried by Ubuntu hands. (Note that given bugs on the respective packages, such a change could be done in very few days in Debian.) Not doing it in "Debian first" now means that it might eventually be done there later and that a merge will be needed; that sounds like unneccessary work on both sides (and I like to avoid unneccessary work).

In particular, this topic was previously discussed there: http://lists.debian.org/debian-python/2009/09/msg00132.html and there seemed to be reasonable agreement around a lintian warning and/or python policy amendment (although without actions); this should really come before blindly fixing all affected packages in Ubuntu only. (IMHO, eh).

Cheers, OdyX