Message104123
Removing __future__ as part of explicit command line execution of 2to3 makes some sense, but I wonder if 2to3 is used more often automatically (e.g. via Distribute) where it's at best unhelpful. 2to3 is all about making it easy to port code from Python 2 to 3, and this particular transformation makes it (albeit, slightly so) harder.
A different idea would be to add a comment before the future import indicating its uselessness, but not removing it. OTOH, I would also be happy with a better way to just disable it in a setup.py (e.g. by passing the -x flag in somehow). |
|
Date |
User |
Action |
Args |
2010-04-24 19:27:35 | barry | set | recipients:
+ barry, benjamin.peterson, eric.araujo |
2010-04-24 19:27:35 | barry | set | messageid: <1272137255.2.0.0311426370261.issue8505@psf.upfronthosting.co.za> |
2010-04-24 19:27:33 | barry | link | issue8505 messages |
2010-04-24 19:27:33 | barry | create | |
|