[issue2353] Use of file.xreadlines() should raise a Py3K warning

Georg Brandl <[EMAIL PROTECTED]> added the comment: Committed slightly reviewed patch and test in r63340. -- nosy: +georg.brandl resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue2353] Use of file.xreadlines() should raise a Py3K warning

Douglas Mayle <[EMAIL PROTECTED]> added the comment: I should note that test_normalization fails with or without the patch, so no change __ Tracker <[EMAIL PROTECTED]> __ __

[issue2353] Use of file.xreadlines() should raise a Py3K warning

Douglas Mayle <[EMAIL PROTECTED]> added the comment: Since file() is removed from 3k, this error message tries to be as generic as possible. We should also warn on any use of file() instead of open() Also, all tests have passed except test_normalization -- keywords: +patch Added file: h

[issue2353] Use of file.xreadlines() should raise a Py3K warning

Douglas Mayle <[EMAIL PROTECTED]> added the comment: I'm on it... -- nosy: +douglas __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list maili

[issue2353] Use of file.xreadlines() should raise a Py3K warning

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

[issue2353] Use of file.xreadlines() should raise a Py3K warning

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