On Sun, 29 Mar 2009, Karsten Hilbert wrote:
Well, you are trying to solve two things at once:
1) make the "python -m" calling convention work
2) move GNUmed modules to a private location
While, yes, this WAS recommended in that report I tried furiously
to argue against doing both at once because only the first is needed
to deal with the actual bug raised.
While it is tempting to "slip in" not strictly needed improvements into
a bugfix it is usually - as is quite evident here - a road down which
dragons live.
Don't.
Well, I didn't in the first place (look at 0.3.12 package). But since
0.4.x it stopped working this way - so I tried to apply the recommendations
of the updated Python policy from scratch.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
