On Wed, Feb 25, 2009 at 1:46 PM, Antoine Pitrou wrote:
> Guido van Rossum python.org> writes:
>>
>> However that's hardly an ABC. You need to provide a path for someone
>> who wants to implement the ABC without inheriting your implementation.
>
> I may missing something, but it's exactly the same
Guido van Rossum python.org> writes:
>
> However that's hardly an ABC. You need to provide a path for someone
> who wants to implement the ABC without inheriting your implementation.
I may missing something, but it's exactly the same as today's io.py: if you
derive the ABC, you inherit the imple
On Wed, Feb 25, 2009 at 1:31 PM, Nick Coghlan wrote:
> Guido van Rossum wrote:
>> On Wed, Feb 25, 2009 at 1:03 PM, Antoine Pitrou wrote:
>>> Guido van Rossum python.org> writes:
Without a shared ABC you'd defeat the whole point of having ABCs.
However, importing ABCs (which are de
Guido van Rossum wrote:
> On Wed, Feb 25, 2009 at 1:03 PM, Antoine Pitrou wrote:
>> Guido van Rossum python.org> writes:
>>> Without a shared ABC you'd defeat the whole point of having ABCs.
>>>
>>> However, importing ABCs (which are defined in Python) from C code
>>> (especially such fundamental
On Wed, Feb 25, 2009 at 1:03 PM, Antoine Pitrou wrote:
> Guido van Rossum python.org> writes:
>>
>> Without a shared ABC you'd defeat the whole point of having ABCs.
>>
>> However, importing ABCs (which are defined in Python) from C code
>> (especially such fundamental C code as the I/O library)
Guido van Rossum python.org> writes:
>
> Without a shared ABC you'd defeat the whole point of having ABCs.
>
> However, importing ABCs (which are defined in Python) from C code
> (especially such fundamental C code as the I/O library) is really
> subtle and best avoided.
>
> In io.py I solved t
On Wed, Feb 25, 2009 at 7:35 AM, Antoine Pitrou wrote:
> I would like to know if both IO implementations (the C one and the Python one)
> should share their ABCs (IOBase, RawIOBase, etc.). It looks preferable to me
> but
> since I'm not very familiar with ABCs I'd like to be sure it's the good
>
Hello,
I would like to know if both IO implementations (the C one and the Python one)
should share their ABCs (IOBase, RawIOBase, etc.). It looks preferable to me but
since I'm not very familiar with ABCs I'd like to be sure it's the good choice.
(of course, the *implementations* won't be shared
