From: Frank T. <ft...@ne...> - 2002-07-19 03:27:09
|
Juergen Hermann, on 2002-07-12, wrote: > You could also open a new CVS module, and a new package in the release > section. But this is totally up to you. Doing it this way, I'm trying to figure out how get the installed aop module named something like pythius.aop. The trouble is that in order to have pythius.aop, pythius/__init__.py needs to exist (to indicate that pythius/ is a package directory). The current pythius distribution gives this file (so things like pythius.util and pythius.grok can exist), so if a separate pythius.aop distribution gave it also, we would have two separate distributions giving the same file. Until about 5 minutes ago, I didn't have an idea on how to approach this cleanly, but now I think I have a solution. In noting that pythius/__init.__.py doesn't really do anything, I think the way to do this would be to have both packages give the file, but have it be a zero-length file. This way, there would be 'change' if you happened to install old-style pythius or pythius.aop first, and followed it up with the other. Does a zero-length pythius/__init__.py seem like a good solution? -- Frank Tobin http://www.neverending.org/~ftobin/ |