On Tue, 28 Apr 2009, Yaakov Nemoy wrote:
#1 works because there's a precedent that applications that are
really
just entrypoints into python library code should be named like a
library. If nothing else, there would be a definite 'python-ekg'
package no matter what. I could split it off with subpackages too.
I guess that's ok with me. No strong feelings either way.
--Max