[issue2359] A Py3K warning for array.array.{read,write} is needed

Georg Brandl <[EMAIL PROTECTED]> added the comment: Committed patch as r61881. -- nosy: +georg.brandl resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue2359] A Py3K warning for array.array.{read,write} is needed

Changes by Jeff Balogh <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file9702/issue2359.diff __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bu

[issue2359] A Py3K warning for array.array.{read,write} is needed

Jeff Balogh <[EMAIL PROTECTED]> added the comment: Attaching a fixed patch that follows PEP 7. Added file: http://bugs.python.org/file9709/issue2359-stylefix.diff __ Tracker <[EMAIL PROTECTED]> __

[issue2359] A Py3K warning for array.array.{read,write} is needed

Jeff Balogh <[EMAIL PROTECTED]> added the comment: Attaching a patch that adds the deprecation warnings. It's a bit dirty because there isn't a read or write function anymore, so I had to make stubs that contain the warnings. -- keywords: +patch Added file: http://bugs.python.org/fil

[issue2359] A Py3K warning for array.array.{read,write} is needed

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

[issue2359] A Py3K warning for array.array.{read,write} is needed

Jeff Balogh <[EMAIL PROTECTED]> added the comment: I've got this one. -- nosy: +jbalogh __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list m

[issue2359] A Py3K warning for array.array.{read,write} is needed

New submission from Brett Cannon <[EMAIL PROTECTED]>: array.{read,write} from the array module should raise at least a Py3K warning, if not a DeprecationWarning. -- components: Interpreter Core keywords: 26backport messages: 63735 nosy: brett.cannon priority: immediate severity: normal s