Hacker News Reader

Comment by prox | Hacker News Reader

Another problem is that the code changes from version to version, so a big chance that example you found no longer works. While annoying it’s not insurmountable, but a good doc would help a lot indeed! Perhaps with the LTS release that’s a thing to solve.

View on HN

Unless the example is from 2.79 and earlier it shouldn't take any or only minimal adjustments. There have been some API changes between versions since 2.81, but they usually wouldn't affect a lot of add-ons or are very easy to change.

All the API changes are also documented in the release notes [0] and the API docs allow to view the Python API for each version [1].

What change between versions caused you problems and what parts of the API docs were lacking?

[0] https://wiki.blender.org/wiki/Reference/Release_Notes [1] https://docs.blender.org/api/current/index.html

Upgrading your plugins is not so much a problem.

What is a problem, though, is that when you google an issue, and find a solution, you then have to upgrade that solution to your version of Blender. That is very annoying because unless you're familiar with Blender, you can't tell if the solution is wrong, or correct but outdated.

From my experience script examples usually indicate what version they were made for and add-ons have to declare the minimum supported Blender version in their `bl_info`, which tells what API version it was implemented for. I know that at least on Blender's Stack Exchange the community tries to provide updated answers if anything relevant has changed in a new version.

I can see that older scripts for 2.79 and earlier may cause the issue you're describing, but this doesn't seem like a Blender specific issue. How did Maya handle API changes between versions? I would assume that there were breaking changes at some point that caused similar issues.

Reply on news.ycombinator.com