[Bf-python] Ipo/IpoCurve API revisited

[cpbarton at iinet.net.au]

Could modules that have improved functionality, but break backwards
compatibility, be commited under FooBar_dev?

eg.
import Ipo_dev as Ipo

Then we could just add in modules when there coded and not worry about breaking
anything, also allows for more time to make changes before a release.

Also Commentingout the _dev modules if needs be. is no big deal. about 3 lines
for each module.

Once people are happy with them, we can choose to replace the old modules.

Toni was suggesting have Blender_dev, not bad but not sure how to do that.
- Cam

> Ken Hughes wrote:
> > Just a follow-up on this now-three-month-dormant code:  since I've got 
> > the time to revive it, and since I was holding off commiting until I saw 
> > the direction that the API rewrite was taking (which apparently for now 
> > is "no rewrite") I'll be readying the code to commit in the next week or 
> > so unless there are some really strong arguments not to.  In the 
> > meantime I'll start the documentation changes.
> 
> This didn't tkae as long as I thought it would.  However, I'm going to 
> be out-of-town for a few days and don't want to commit anything which 
> might break something (I've tested but not ultra-thoroughly) so I put it 
> on the patch tracker in case someone wants to play with it:
> 
>
https://projects.blender.org/tracker/index.php?func=detail&aid=4001&group_id=9&atid=127
> 
> Ken
> _______________________________________________
> Bf-python mailing list
> Bf-python at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-python
>