Hi, all! I am striving to make some python UNO components work for 2.0.2 on linux, while they worked fine for the previous stable version (on any system). I am still trying to isolate the problem so I can post an issue, but I guess I'll tell my story anyway to see if anybody has experienced anything similar or has any clue to offer.
At first I had problems both on linux and Windows. What happened was that the first time I ran a VB macro instantiating my python components everything went ok. It was just when trying to run again that the system blocked forever. On windows, it was necessary to kill OOo and exit the quickstarted to be able to run once again (and have the system block the following time). I found out that one object - say SomeObj - created by the UNO package kept references to some XEnumeration objects. As far as I understand, this should make no difference as long as SomeObj was unreachable after completion of the macro. However, when I ensured all those references were None-ified, the problem disappeared on Windows, persisting on Linux though. An amazing detail: if a print command is added to the VB macro before the components are instantiated, the problem disappears. Please do not tell me off for not posting code. I am working on that at the moment, but it's not that easy given the size of the system. Cheers, Jorge. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
