Wed, 08 Jan 2003 09:43:59 -0800
Sorry to interject in something that's not my domain but ... it seems
that part of the problem is that there are no constraints about what the
Python API really is.
In my mind the best way to get the current contraints would be to gather
a collection of tools written for/in blender & use them as a regresion
That way you always know what is working at the minimum.
Just my 2 cents,
Ton Roosendaal wrote:
> Hi Jacek & everyone here,
> Python in Blender always has been a very complex thing to implement and
> maintain. Each developer at NaN who worked at it had a different vision
> on it...
> Daniel Dunbar did the first implementation (1.5), and changed it
> halfway (1.8). Then Jan Walter revised it (2.0), and made it quite more
> complete. Erwin Coumans added the Game Engine API in a different way
> (2.1). And finally Martin Strubel tried to get Python up to a more
> mature level in Blender (2.2), but he got stuck...
> I've had no direct involvement with the implementation itself. I only
> kept saying "keep it compatible" and "make sure it works". But that's
> something people don't like to do, it seems...
> For Python in Blender to really work, we need a strict Python board
> acting as a watchdog & gatekeeper on the actual implementation.
> Preferably a mixed group of diehard coders and actual users of
> Blender's Python. At the Python discussion board I already did a call
> for participation a couple of months ago. I will repeat that call, and
> also now here:
> Anyone interested in maintaining and further improving Python in
> Blender? I prefer to make this a seperate project at our
> projects.blender.org site. Not only for the current 2.2x Blenders, but
> especially for the future, Python will play an increasingly important
> role... so there's quite some work to do, and honour to gather in this
> job! :-)
> On Tuesday, Jan 7, 2003, at 18:50 Europe/Amsterdam, Michel Selten wrote:
>> On Mon, 2003-01-06 at 21:37, Jacek Popławski wrote:
>>> It's probably bad place to say that, but I am searching for people
>>> with fixing/changing Python API so we could discuss it. Please tell
>>> me where
>>> should I go.
>> In my opinion this is a perfect place to ask questions like you did :)
>> Here is my idea on what should happen with the Python API:
>> Get Python support back in Blender to the point it supports the same API
>> as it did in the NaN days. In other words, for the end-user nothing
>> seems to have changed.
>> In future versions (at least after the feature freeze), design and
>> implement new features for the Python API. In my opinion any new
>> implementation of the API should be backwards compatible with older
>> versions of Blender.
>> With regards,
>> Bf-committers mailing list
> ------------------------------------------------------------------------ --
> Ton Roosendaal Blender Foundation email@example.com
> Bf-committers mailing list