[Python-Dev] State of PEP-3118 (memoryview part) (original) (raw)
Matt Joiner anacrolix at gmail.com
Sun Feb 26 16:11:42 CET 2012
- Previous message: [Python-Dev] State of PEP-3118 (memoryview part)
- Next message: [Python-Dev] State of PEP-3118 (memoryview part)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
+1 for won't fix. On Feb 26, 2012 9:46 PM, "Antoine Pitrou" <solipsis at pitrou.net> wrote:
On Sun, 26 Feb 2012 14:27:21 +0100 Stefan Krah <stefan at bytereef.org> wrote: > > The underlying problems with memoryview were intricate and required > a long discussion (issue #10181) that led to a complete rewrite > of memoryobject.c. > > > We have several options with regard to 2.7 and 3.2: > > 1) Won't fix.
Given the extent of the rewrite, this one has my preference. Regards Antoine.
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/anacrolix%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120226/93115d90/attachment.html>
- Previous message: [Python-Dev] State of PEP-3118 (memoryview part)
- Next message: [Python-Dev] State of PEP-3118 (memoryview part)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]