➜
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.
Created on 2008-03-20 19:08 by eric.smith, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg64193 - (view) | Author: Eric V. Smith (eric.smith) *  |
Date: 2008-03-20 19:08 | |
Should this be accepted in 3.0, and become a no-op: from __future__ import print_function ? It might make using code in 2.6 and 3.0 easier, since you would not have to delete this line. I note that: from __future__ import with_statement is already valid in 3.0. |
|||
| msg64195 - (view) | Author: Christian Heimes (christian.heimes) * |
Date: 2008-03-20 19:10 | |
Yes, you *must* implement it. From http://docs.python.org/lib/module-future.html No feature description will ever be deleted from __future__. |
|||
| msg64221 - (view) | Author: Eric V. Smith (eric.smith) * |
Date: 2008-03-20 23:02 | |
Implemented in r61682. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:32 | admin | set | github: 46688 |
| 2008-03-20 23:02:59 | eric.smith | set | status: open -> closed resolution: accepted -> fixed messages: + msg64221 |
| 2008-03-20 19:10:52 | christian.heimes | set | resolution: accepted messages: + msg64195 nosy: + christian.heimes |
| 2008-03-20 19:08:18 | eric.smith | create | |