Id like to hear what API changes cause problems. * if its one large change that causes problems for every one using the api (bmesh, pynodes) * if its misc changes in blender which propagate down into the api - (recent premul/alpha changes). * if its from being strict and adding limits like the restricted context, or disallowing data editing during drawing. (things that shouldn't be done anyway). * if its even intentional/known-about - Some end up being side effects of other changes in blender.
On Sun, May 26, 2013 at 10:59 PM, Ton Roosendaal <t...@blender.org> wrote: > Hi, > > Excellent, we do have a API change page :) > http://wiki.blender.org/index.php/Extensions:2.6/Py/API_Changes > > Should get more prominent linking everywhere! > > -Ton- > > -------------------------------------------------------- > Ton Roosendaal - t...@blender.org - www.blender.org > Chairman Blender Foundation - Producer Blender Institute > Entrepotdok 57A - 1018AD Amsterdam - The Netherlands > > > > On 26 May, 2013, at 13:23, Ton Roosendaal wrote: > >> Hi all, >> >> This is probably just coincidentally, but just in past few days two quite >> visible py scripters moaned in public about API breakage, more or less >> mentioning to give up on it. >> >> Communication is really King here. That means for every release, a simple >> quick to find doc with API changes has to be available (or is there one?). >> >> We can also reconfirm the procedures for api changes, to go along our >> release cycle: >> >> - Announce in BCon1 or BCon2. >> - Add it in BCon2 latest. >> - Testing, feedback during BCon3 and BCon4. >> >> We also have a bf-python mailing list where these topics are valid to >> discuss. I think every API change should be a topic for review there as >> well. It probably is? :) >> >> I think by default scripters can expect the API to keep working. Checking >> back on the history of Python script breakage discussion here, it appeared >> the changes were more related to "keep a good quality and sane API". Our >> scripting API is also powerful, and if you find smart bypasses for >> undocumented or accidentally working features, things can get frustrated... >> >> If you depend on the API to keep working, please consider to join bf-python, >> and help us out with reviews and design decisions! >> >> Thanks, >> >> -Ton- >> >> -------------------------------------------------------- >> Ton Roosendaal - t...@blender.org - www.blender.org >> Chairman Blender Foundation - Producer Blender Institute >> Entrepotdok 57A - 1018AD Amsterdam - The Netherlands >> >> >> >> _______________________________________________ >> Bf-committers mailing list >> Bf-committers@blender.org >> http://lists.blender.org/mailman/listinfo/bf-committers > > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
