Future compatibility of the Python C API

[Richard Brodie]

"Mark Hammond" <mhammond at skippinet.com.au> wrote in message
news:q4FJ4.1198$1D.10037 at news-server.bigpond.net.au...

> > My big concern is Python 3000- what are the odds
> > that its C API will be backwards compatibility with Python 1.x?
>
> Not very good.  If it is a real problem, simply dont upgrade.  I would
> however expect the changes to cause compiler errors that are simple to
> fix - ie, very similar APIs, and unlikely to silently change behaviour.

I suppose that someone out there is working on persuading SWIG to
generate suitable wrapper code? It would be a pain if there were a
long transitional period when you had to go back to handcrafting
wrapper code. No doubt doing so for the whole of win32 would keep
you out of trouble a while ;)