On Sun, 2006-09-04 at 11:42 -0700, Zac Medico wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Brian wrote: > > Just a word of caution. I don't know why but sometimes after an upgrade > > of portage a reload(portage) in porthole fails and porthole crashes. I > > don't remember the details atm and have not investigated the reasons. > > In all cases restarting porthole, all works fine again. It may not ever > > happen to your code though. > > If you're able to reproduce that with the latest ~arch version of portage > then I would appreciate it if you'd file a bug. > > Zac
OK, so I had another crash this morning after upgrading portage from 2.1_pre7-r5 to 2.1_pre9-r5 and trying to reload(portage). The crash was repeatable for the current porthole session. Again, quiting porthole and restarting, it works properly, and reload(portage) works without error. This time the error was: (brief snipit of pycrash output) Thread Name: MainThread Exception Type: exceptions.AttributeError Exception Value: 'module' object has no attribute 'LazyItemsDict' Frame Name: do_vartree Frame Size: 4 File Name: /usr/lib/portage/pym/portage.py Line Number: 6488 I believe what is happening is that when porthole executes the reload(portage) that only portage is being reloaded and not any/all of it's /pym imports. Could that be the cause? If the 'LazyItemsDict' was something changed in one of the portage external modules then that would confirm what I suspect. The full pycrash output can be found here: http://www3.telus.net/dol-sen/porthole/crash_2.1_pre7-r5_to_2.1_pre9-r5.html If you still think I need to file a bug, I will. -- Brian <[EMAIL PROTECTED]> -- [email protected] mailing list
