[Orbit-python-list] Porting to Python 2.0b1
Status: Inactive
Brought to you by:
tack
From: Roland M. <ma...@ec...> - 2000-09-06 16:54:37
|
I got the following message in my server under Python 2.0b1: ** WARNING **: Exception must be derived from CORBA.UserException Using the current CVS code slightly patched: I just commented out the offending code causing errors with threading (reported in another message). This bug happens when I use Python 2.0b1 but not when I use Python 1.5.2. After a bit of searching, it appears that the function init_exceptions() (in src/except.c) is not called. After another bit of searching, it appears that init_exceptions() is in fact called, but unfortunately it's not ours. I don't know what Python 2.0b1's does, but I'm pretty confident ;-) that it does not create the CORBA.UserException and CORBA.SystemException exceptions. I therefore suggest renaming at least some of ORBit-Python's functions to something with a prefix (I used "OPY_" as a quick hack, but I don't intend to keep it). I'll grep through the sources of ORBit-Python, then nm through libpython2.0.a, see the intersection of the function names thusly obtained, and rename them. Expect a series of CVS commits soon :-) BTW: how do I add a conditional to ./configure so that I can keep the threading support out? (Or alternatively, when will it be fixed? :-) (BTW² for Jason: I'll also have a look at the memory leaks, since I still encounter them. You have any ideas where to look?) Have fun, Roland. -- Roland Mas Mou ichido ! Hayaku ! Ookii koede ! -- Atsuko Sasaki |