New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change buffer/memoryview DeprecationWarning #47756
Comments
Right now in 2.6, using buffer() warns that it is going away and to use That means the warning is covering something that is within 2to3's |
Definitely don't bring buffer() back in 3.0! It needs to die. If 2to3 can do this reasonably well, let's do that. |
On Tue, Aug 5, 2008 at 12:41 PM, Guido van Rossum
There is already a fixer to go from buffer() to memoryview(), but I |
The memoryview implementation is still unfinished (in py3k), so I |
How unfinished is it, Antoine? So much that it can't be used, or just to |
I'm no buffer API/memoryview expert, but at least slicing is not Hopefully Travis will be able to enlighten us when he is back. |
On Wed, Aug 6, 2008 at 12:32 PM, Antoine Pitrou <report@bugs.python.org> wrote:
Well, if it can't replace buffer() then the warning needs to change to
Hopefully. |
+1. buffer() stinks. memoryview() rules. They don't hvae the same use Is there truly nobody else who understands PEP-3118 well enough? |
On Wed, Aug 6, 2008 at 1:12 PM, Guido van Rossum <report@bugs.python.org> wrote:
That settles that then.
Not me. |
Le mercredi 06 août 2008 à 20:12 +0000, Guido van Rossum a écrit :
PEP-3118 is not very detailed (for example the exact semantics of |
In r65584 I changed the warning to not mention memoryview(); it just |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: