On Mon, Apr 7, 2014 at 1:11 PM, Benjamin Peterson <benjamin at python.org> wrote: > > > We can populate that struct with array-specific alternatives for > > PySequence/PyMappingMethods and eliminate the need for dynamically > > created array types to allocate those. > > Why would we want to do that? I assume "that" means "create array types dynamically." There are many reasons to do that in modern array implementations. See for example ctypes. A more practical reason however is that I believe PySequence/PyMappingMethods are cloned whenever a subclass of a sequence/mapping type is created. For better or worse, subclassing of numpy arrays is a popular sport these days. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140407/126ce55b/attachment-0001.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4