[Python-Dev] mmap feature or bug?

[Josiah Carlson]

Quick questions:
Is mmap's inability to be subclassed a feature or bug?
Is one's inability to use a = mmapinstance.__setslice__;a(1,2,'a') (and
others) a feature or bug?

I would imagine they are bugs, but I just wanted to make sure and post
the report/request in the proper location.

Thank you,
 - Josiah

___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] mmap feature or bug?

[Martin v. Löwis]

Josiah Carlson wrote:
Is mmap's inability to be subclassed a feature or bug?
No.
It's a missing feature: it's not a bug, because nobody says this should
work, and anybody trying will find out that it doesn't work, so nobody
is tricked into believing it should work. The mmap type is not even
documented; mmap.mmap is a function.
It's not a feature, because (atleast IMO) there would be nothing wrong
with making mmap.mmap a subclassable type.
Is one's inability to use a = mmapinstance.__setslice__;a(1,2,'a') (and
others) a feature or bug?
That is a bug. Slice assignments are supported, and so should
__setslice__.
Regards,
Martin
___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com