Movatterモバイル変換
[0]ホーム
[Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python
Mark HammondMarkH@ActiveState.com
Sun, 6 Aug 2000 15:08:46 +1000
[/F]> > huh? are you seriously proposing to break every single C extension> > ever written -- on each and every platform -- just to trap an error> > message caused by extensions linked against 1.5.2 on your favourite> > platform?[Barry]> What makes you think that a crash will not happen under Unix> when you change the API? You just don't get the Windows crash.>> As this thread has pointed out you have no intention of checking> for binary compatibility on the API as you move up versions.I imtimated the following, but did not spell it out, so I will here toclarify.I was -1 on Barry's solution getting into 1.6, given the time frame. Ihinted that the solution Guido recently checked in "if(!Py_IsInitialized()) ..." would not be too great an impact even if Barry'ssolution, or one like it, was eventually adopted.So I think that the adoption of our half-solution (ie, we are really onlyforcing a better error message - not even getting a traceback to indicate_which_ module fails) need not preclude a better solution when we have moretime to implement it...Mark.
[8]ページ先頭