Cool PEP! I really love the API for the Image class. A standard Image
class would be a useful addition to the standard library.
But I cannot see how it would solve the problem with to many image
classes. The reason why PIL, PyGame and wxPython has different image
classes is because each of them us
BJörn Lindqvist schrieb:
> Cool PEP! I really love the API for the Image class. A standard Image
> class would be a useful addition to the standard library.
>
> But I cannot see how it would solve the problem with to many image
> classes. The reason why PIL, PyGame and wxPython has different image
>> The only way to get compatibility between the libraries is to create
>> an image library in C _and_ get those libraries to start using it.
>>
>
> They'll all quack the same way. (This is paraphrased in the PEP's
> abstract, as far as I read it.)
To the Python side, yes. But to the underlying
2007/7/1, BJörn Lindqvist <[EMAIL PROTECTED]>:
> But I cannot see how it would solve the problem with to many image
> classes. The reason why PIL, PyGame and wxPython has different image
> classes is because each of them use different C functions for
> manipulating said image classes. These differe
