This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients brett.cannon, gvanrossum
Date 2008-08-05.22:52:41
SpamBayes Score 0.0073189074
Marked as misclassified No
Message-id <bbaeab100808051552k91a5c09lb06d0281189a24bd@mail.gmail.com>
In-reply-to <1217965278.53.0.655381868317.issue3506@psf.upfronthosting.co.za>
Content
On Tue, Aug 5, 2008 at 12:41 PM, Guido van Rossum
<report@bugs.python.org> wrote:
>
> Guido van Rossum <guido@python.org> added the comment:
>
> Definitely don't bring buffer() back in 3.0!  It needs to die.
>
> If 2to3 can do this reasonably well, let's do that.
>

There is already a fixer to go from buffer() to memoryview(), but I
don't know how compatible the APIs are. That might still require a
warning.
History
Date User Action Args
2008-08-05 22:52:44brett.cannonsetrecipients: + brett.cannon, gvanrossum
2008-08-05 22:52:42brett.cannonlinkissue3506 messages
2008-08-05 22:52:41brett.cannoncreate