[Bf-python] integrating lib iter types

[Joe Eagar]

Joseph Gilbert wrote:
> The tradeoff is duplication of code in the codebase.  We have 
> discussed "from __future__ import Blender" before. I don't think it a 
> bad idea, but we need to increase the size of the codebase in blender 
> to have separate C files for all this stuff.  If we want to do this 
> its a major design change.
>
> Otherwise, any new functionality should:
> a) never break old functionality until we are ready to do so
> b) deprecate the old functionality to allow users to switch to the new 
> code.
Should we plan on maybe calling the new module (if indeed that's the 
direction we're going) "blender" rather then "Blender"?  The idea being 
that old scripts can use the "Blender" module and new scripts can use 
"blender".  This would allow us to maintain backwards compatibility.

Joe