Future compatibility of the Python C API

[Richard Brodie]

"Remco Gerlich" <scarblac-spamtrap at pino.selwerd.nl> wrote in message
news:slrn8fed2o.4fe.scarblac-spamtrap at flits104-37.flits.rug.nl...

> > I suppose that someone out there is working on persuading SWIG to
> > generate suitable wrapper code?
>
> Since noone knows what Python 3000 is going to look like yet, that would be
> very hard, wouldn't it? :)

Well possibly. However, I assumed that someone has an idea how it should
look. I presumed that one would not start by assuming that there wouldn't be
backwards compatibility, until far enough down the design to see that it
wouldn't be practical. Unless you work for MS, lack of compatibility isn't
usually a design goal.