When the new API is ready, hopefully for Blender 2.28, is there any chance of having some backwards compatibility? As it is now, some scripts work in 2.23, some in 2.26/2.27 and some in both. This is difficult to keep track of, especially if you don’t use the scripts very often. I’d like very much to be able to run all scripts in the same Blender version.
Please…
Hans Petter
Make it so we can import the old api if we need to, or rename the new api such as Blender28 etc, lots of good scripts out there using old api’s.
Hi,
This should have been added to the status report when it was posted on blender.org. Most of the developers on the mailing list know the reason behind the Python api rewrite. So I saw no reason for adding yet another explanation 
The implementation of the Python api in 2.23 and 2.25 is very difficult to read. Another problem was that it causes some build problems. Extending the current API is rather difficult. Those were some of the reasons for me to take on the challenge to rewrite the entire Python API in blender. The most important thing I kept in my mind though, was to keep the API 100% compatible with 2.23 and 2.25. As a user I would hate to see that I had to rewrite my scripts again :-? .
Now, with some new developers joining the effort, the work is speeding up. Some new additions are being made to the API too. See the status report on blender.org.
So far the compatibility thing is working out, if there’s a difference, it’s because of a fault in 2.23/2.25.
If there’s going to be a compatibility problem (we aren’t finished with the implementation, so these might come up), then we will mention those of course, and try to present an alternative.
The blender210 api is not coming back. Unless somebody else wants to take up that task of course.
Hope this gives you enough information.
With regards,
Michel
Thanks, that was just waht I wanted to know!
Hans Petter