>From my PoV of "ecosystem" breakage is not as much an issue as is proactive
>notification. I don't see adding more code to maintain as a good ROI balance.
To quote my previous post on the matter..."The
center of gravity that I am inferring is an improved predictability
balance as in an ecological system. The emphasis is on balance as much
as predictability. ... Something more proactive than reactive
from this vantage point improves the return on investment of time."
The devs have quite a bull to fight and I sincerely appreciate their matador
heroics. If we can manage the surprises better, devs on the sideline of the
ring will spill less popcorn and enjoy the show more IMHO.
JTa
________________________________
From: Asbjørn <[email protected]>
To: Blender Foundation Python list <[email protected]>
Sent: Tuesday, July 9, 2013 6:04 PM
Subject: Re: [Bf-python] No More Renaming or Alias Vol 101, Issue 3 (Squeaky
Wheel)
On 10.07.2013 02:27, Campbell Barton wrote:
> Between 2.67 and 2.68 Blenders python API broke again (it sounds
> dramatic, some very small things changed...)
> - an redundant BMesh operator that wasn't used anywhere was removed,
> its possible a script used it though.
> - weight paint operators arguments and behavior changed.
> - recalculate normals had an argument removed (which wasn't needed).
Unless I'm mistaken, some custom node draw function changed parameter
count, breaking LuxBlender. Then again, custom nodes is quite fresh so
breakages are kinda expected there for a while.
- Asbjørn
_______________________________________________
Bf-python mailing list
[email protected]
http://lists.blender.org/mailman/listinfo/bf-python
_______________________________________________
Bf-python mailing list
[email protected]
http://lists.blender.org/mailman/listinfo/bf-python
