[issue3506] Change buffer/memoryview DeprecationWarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: In r65584 I changed the warning to not mention memoryview(); it just says that buffer() does not exist in 3.0. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <

[issue3506] Change buffer/memoryview DeprecationWarning

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Le mercredi 06 août 2008 à 20:12 +, Guido van Rossum a écrit : > +1. buffer() stinks. memoryview() rules. They don't hvae the same use > cases. > > Is there truly nobody else who understands PEP 3118 well enough? PEP 3118 is not very

[issue3506] Change buffer/memoryview DeprecationWarning

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- assignee: -> brett.cannon ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-li

[issue3506] Change buffer/memoryview DeprecationWarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Wed, Aug 6, 2008 at 1:12 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > Guido van Rossum <[EMAIL PROTECTED]> added the comment: > >> Well, if it can't replace buffer() then the warning needs to change to >> just flat-out state that buffe

[issue3506] Change buffer/memoryview DeprecationWarning

Guido van Rossum <[EMAIL PROTECTED]> added the comment: > Well, if it can't replace buffer() then the warning needs to change to > just flat-out state that buffer() is gone and not suggest any > replacement. +1. buffer() stinks. memoryview() rules. They don't hvae the same use cases. Is ther

[issue3506] Change buffer/memoryview DeprecationWarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Wed, Aug 6, 2008 at 12:32 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > I'm no buffer API/memoryview expert, but at least slicing is not > implemented, and there are almost no unit

[issue3506] Change buffer/memoryview DeprecationWarning

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: I'm no buffer API/memoryview expert, but at least slicing is not implemented, and there are almost no unit tests. It can probably be used, but given the absence of tests and of actual uses in the stdlib, I'm not sure we can say it is robust an

[issue3506] Change buffer/memoryview DeprecationWarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: How unfinished is it, Antoine? So much that it can't be used, or just to the extent it doesn't take the same arguments as buffer()? If it is the latter then the warning should be changed to warn about unsupported arguments.

[issue3506] Change buffer/memoryview DeprecationWarning

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: The memoryview implementation is still unfinished (in py3k), so I suggest we drop the warning or comment it out. -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]>

[issue3506] Change buffer/memoryview DeprecationWarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Tue, Aug 5, 2008 at 12:41 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > Guido van Rossum <[EMAIL PROTECTED]> added the comment: > > Definitely don't bring buffer() back in 3.0! It needs to die. > > If 2to3 can do this reasonably well,

[issue3506] Change buffer/memoryview DeprecationWarning

Guido van Rossum <[EMAIL PROTECTED]> 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. -- nosy: +gvanrossum ___ Python tracker <[EMAIL PROTECTED]>

[issue3506] Change buffer/memoryview DeprecationWarning

New submission from Brett Cannon <[EMAIL PROTECTED]>: Right now in 2.6, using buffer() warns that it is going away and to use memoryview(). Unfortunately memoryview() won't be backported to 2.6 in time for release. That means the warning is covering something that is within 2to3's realm. So the