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 2010-04-23 12:31 by barry, last changed 2022-04-11 14:57 by admin. This issue is now closed.
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:57:00 | admin | set | github: 52751 |
2010-04-24 19:34:21 | barry | set | messages: + msg104125 |
2010-04-24 19:30:38 | benjamin.peterson | set | status: open -> closed resolution: works for me |
2010-04-24 19:29:26 | benjamin.peterson | set | messages:
+ msg104124 title: 2to3 fix_future.py removes __future__ imports, but should it? -> 2to3 fix_future.py removes __future__ imports, but should it? |
2010-04-24 19:27:33 | barry | set | messages: + msg104123 |
2010-04-24 17:12:07 | eric.araujo | set | messages:
+ msg104105 title: 2to3 fix_future.py removes __future__ imports, but should it? -> 2to3 fix_future.py removes __future__ imports, but should it? |
2010-04-24 17:10:44 | eric.araujo | set | nosy:
+ eric.araujo messages: + msg104104 |
2010-04-23 20:39:18 | benjamin.peterson | set | nosy:
+ benjamin.peterson messages: + msg104049 |
2010-04-23 12:31:14 | barry | create |