[Bf-python] new python development path

[Gilbert, Joseph T.]

This was suggested before. Something like: from __future__ import
blender2.5 or something. 

I don't know if this would work or not. There might by namespace or
typeobject name conflicts if you import blender and blenderdev at the
same time. If you had this feature the development section would need

1) it's own separate internal file structure in the code with a copy of
all the python files (I think we are planning this anyway)
2) possibly development specific type object naming for namespace
conflicts (would have to investigate)
3) it's own 'blender' init module added to the initialization table for
the interpreter.

It would be nice to have the development api importable as a from
__future__. This would save people the headache of development api
changes constantly sneaking in. The old api would be replaced at some
set time (this would take care of deprecation too) and script writers
could test the dev features in the meantime. 

It def. would not make _less_ work for developers that's for sure but it
would make the user's life easier.

IF/DEF is not a good idea IMHO. This will simply make the code
unreadable. If we do a separate dev section of the code it needs it's
own file hierarchy.

-----Original Message-----
From: bf-python-bounces at projects.blender.org
[mailto:bf-python-bounces at projects.blender.org] On Behalf Of Campbell
Barton
Sent: Wednesday, February 08, 2006 8:23 PM
To: Blender Foundation Python list
Subject: [Bf-python] new python development path

Hey All.

Not sure how big a project this python upgrade is (tp/get/set stuff as 
well as new design) - But was wondering weather its fair to expect one 
of the python gurus willian/stivs/ken to magically come up with the new 
python code.

A possible way to develop a new python without putting so much pressure 
on said gurus, could be to have a parallel Python module cell it 
BlenderDev for eg..
import BlenderDev as Blender
This would have IFDEFS about it so at any time a release can be made 
without BlenderDev

To start with it would be the same as the existing module, we could 
choose 1 module, World? Lamp?, Mesh? - possibly a smallish module that 
does not depend too much on other modules.

This module could be worked on and made and example, well designed, 
get/set stuff and epydoc's generated from the docstrings.
Once we were happy with it.. other people could go and update/rewrite 
the other Modules Object, World, Scene etc..

- Cam

-- 
Campbell J Barton

133 Hope Street
Geelong West, Victoria 3218 Australia

URL:    http://www.metavr.com
e-mail: cbarton at metavr.com
phone: AU (03) 5229 0241
_______________________________________________
Bf-python mailing list
Bf-python at projects.blender.org
http://projects.blender.org/mailman/listinfo/bf-python