[Bf-committers] I volunteer to maintain the 'deprecated' BGE python methods
dfelinto at gmail.com
Wed May 6 19:43:43 CEST 2009
But are you proposing to remove the old API from the result of 'print
Or only from the online pyDocs?
2009/5/6 <blender at erwincoumans.com>
> I am against the plans to remove the deprecated methods in the BGE python
> API (setPosition etc.), and volunteer to maintain those methods myself.
> (new members have been introduced to the Blender game engine python API, to
> make it easier to access and assign data. obA.position = [1,2,3] instead of
> method obA.setPosition(1,2,3)
> 1) increased compatibility with recent BGE books.
> 2) it is easier to upgrade old scripts to Blender 2.5 and later
> 3) always the option to using methods is more consistent: rather then
> to remember which parts of the API are properties in disguise and which
> still use methods
> 4) there are no big gains of removing the deprecated methods: the new API
> will be tested by all regression tests
> 5) keep the deprecated methods as an undocumented/unofficial feature.
> 6) I'm volunteering myself to maintain them for the time being
> I'm more happy to slowly let this API fade away, and remove them from the
> python self-documentation, and make it an undocumented/unofficial feature.
> So unless there are big objections, please let me just maintain this
> existing BGE python API as an undocumented/unofficial feature. If someone
> tempted to removing the deprecated API, can you please get in touch we me?
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers