➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Deprecate iterable.next in Python > 2.6.x when called with -3 option ?
Type: behavior Stage: test needed
Components: 2to3 (2.x to 3.x conversion tool) Versions: Python 2.7, Python 2.6
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: brett.cannon, georg.brandl, mattrussell
Priority: normal Keywords:

Created on 2009-07-29 23:21 by mattrussell, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg91072 - (view) Author: Matthew Russell (mattrussell) Date: 2009-07-29 23:21 
Not sure if this should be (tentative) feature request or behavior...

It might help new comers and those preparing to port to Python 3.
msg91101 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2009-07-30 17:16 
2to3 already performs the change for calls to iter.next() as well the 
method definition, so a deprecation warning is redundant.

Thanks for the thought, though.
History
Date User Action Args
2022-04-11 14:56:51adminsetgithub: 50846
2009-07-30 17:16:23brett.cannonsetstatus: open -> closed

assignee: georg.brandl ->
components: - Documentation, Interpreter Core

nosy: + brett.cannon
messages: + msg91101
resolution: rejected
stage: test needed
2009-07-29 23:22:11mattrussellsettitle: Depricate iterable.next in Python > 2.6.x when called with -3 option -> Deprecate iterable.next in Python > 2.6.x when called with -3 option ?
2009-07-29 23:21:38mattrussellcreate