On 2000.08.28, in <200008290346.UAA14923@utopia.west.sun.com>, "Dan Mick" <Dan.Mick@West.Sun.COM> wrote:
Actually, from comments in Defaults.py.in, it looks like that should have a from Mailman.Version import VERSION in it, so that importing Defaults or mm_cfg should get it...but I don't know how to use cvs log well enough to find out when the import was dropped from Defaults.py.in
but it does look like a bug all right.
I know enough python to club myself in the head, but I think I hit this one because I had a bug (since resolved) in Defaults.py.[1] If Defaults.py or mm_cfg.py have a traceback error, this looks like it will come up. By importing VERSION explicitly as below, you at least can get the trace informationon the _original_ problem. If it's inherited from Defaults.py, then you still get this problem.
Looks like line 121 of scripts/driver needs to say from Mailman.Version import VERSION instead of from Mailman.mm_cfg import VERSION
Otherwise, I get ImportError during the traceback report.
[1] If you're curious, I modify Defaults.py to have a separate data area from the mailman installation directory. It's an article of faith to me that software directories should be mountable as read-only, so that any mutable data should be in another path. It's also dogma that symlinking your way out of that is non-ideal.
-- -D. dgc@uchicago.edu NSIT University of Chicago