[issue2355] Using buffer() should raise a Py3K warning

Georg Brandl <[EMAIL PROTECTED]> added the comment: Added test and committed as r61878. -- nosy: +georg.brandl resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue2355] Using buffer() should raise a Py3K warning

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: My apologies. I often forget to switch between tabs and spaces for Python and C sometimes. Added file: http://bugs.python.org/file9713/buffer_warning_good_tabbing.patch __ Tracker <[EMAIL PROTECTED]>

[issue2355] Using buffer() should raise a Py3K warning

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: Benjamin, Your recent patches all use 4-space indentation, but Python 2.x recommended style is still to use tabs unless you start a new file. See PEP 7. -- nosy: +belopolsky __ Tracker <[EMAIL

[issue2355] Using buffer() should raise a Py3K warning

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: Are use cases for buffer() satisfied by the new memoryview() builtin? If so, it would be nice to have an automatic conversion or to have the Py3k warning suggest a possible substitute. -- nosy: +rhettinger ___

[issue2355] Using buffer() should raise a Py3K warning

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Here's a patch. -- keywords: +patch nosy: +benjamin.peterson Added file: http://bugs.python.org/file9711/buffer_warning.patch __ Tracker <[EMAIL PROTECTED]> __

[issue2355] Using buffer() should raise a Py3K warning

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- priority: immediate -> urgent __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing lis

[issue2355] Using buffer() should raise a Py3K warning

New submission from Brett Cannon <[EMAIL PROTECTED]>: Using buffer() should raise a Py3K warning. -- components: Interpreter Core keywords: 26backport messages: 63726 nosy: brett.cannon priority: immediate severity: normal status: open title: Using buffer() should raise a Py3K warning ve