[02:34:16] ** vlado has left IRC ("Leaving") [04:00:56] ** vlado has joined us [04:02:36] [connected at Fri Sep 9 04:02:36 2005] [04:02:36] <> *** Looking up your hostname... [04:02:37] <> *** Checking ident [04:02:41] <> *** Found your hostname [04:03:07] <> *** No identd (auth) response [04:03:07] <> *** Your host is brown.freenode.net[brown.freenode.net/6667], running version hyperion-1.0.2 [04:03:07] [I have joined #peak] [04:03:07] ** brown.freenode.net set the topic to PEAK mailing list is back up [06:08:04] ** vlado has left IRC ("Leaving") [08:18:33] ** vlado has joined us [11:11:15] ** vlado has left IRC ("Leaving") [11:23:43] Should PEAK cause any trouble when reloading modules that use it, particularly that use its config, binding, naming, storage, or model subsystems? [11:24:19] I didn't used to have trouble, but since I started using my own ini file more extensively, I've had weird, weird errors. [11:24:42] For example, I found sys.modules[one of my modules] paved over with a copy of peak.storage! [11:25:46] (It was sys.modules['myproject.storage'] that got paved over. A bad assumption about the uniqueness of the last part of the module path somewhere, perhaps?) [11:26:28] I suspect it's these lines from my config file that are triggering the trouble: [11:26:29] [Component Factories] [11:26:29] semreg.model.PersonDMConfigKey = "semreg.storage.PersonDM" [11:44:01] ** erikrose has left IRC () [14:02:05] ** vlado has joined us [14:08:09] ** vlado_ has joined us [14:27:47] ** vlado has left IRC (Read error: 110 (Connection timed out)) [15:37:04] ** pythonhead has joined us