[Bf-python] Image.New()- commit?

[Toni Alatalo]

On Tuesday 13 December 2005 11:43, Campbell Barton wrote:
> Hey Guys

hi

> Have a working Image.New function that I posted a while back. I tested
> and couldent crash it- accounted for stupig input etc.
> Was wondering if I could commit it to bf-blender-

+0

surely this is to be added, and i guess it could be put it to 2.40 still - 
does anyone see anything dangerous here, can we still test more (..as it does 
involve mem. management / refcount related functionality and is hence not 
most trivial)?

if policy strongly suggests, to 2.41 then i guess, but perhaps this is one of 
the 'patching a hole in API is a fix' things?-)

caveat: i dont know the Blender Image code at all.

> - Cam

~Toni

p.s. just yesterday one dev was asking about this functionality, and all we 
knew was to resort to PIL.Image.New() and using Python tmpfiles to open them 
in Blender