Message69619
| Author |
benjamin.peterson |
| Recipients |
benjamin.peterson, collinwinter, kaizhu, loewis, pitrou |
| Date |
2008年07月13日.19:05:23 |
| SpamBayes Score |
0.013776527 |
| Marked as misclassified |
No |
| Message-id |
<1afaf6160807131205w6aaf3c09ud641fcb11e5ecff8@mail.gmail.com> |
| In-reply-to |
<1215975787.47.0.0959957856132.issue3238@psf.upfronthosting.co.za> |
| Content |
On Sun, Jul 13, 2008 at 2:03 PM, kai zhu <report@bugs.python.org> wrote:
>
> kai zhu <davidbranniganz@gmail.com> added the comment:
>
> why not? it allows developers to migrate 2.x scripts one-by-one to
> working 3.0 conformant ones while maintaining backwards-compatibility w/
> existing 2.x scripts & extension modules (eg. numpy, PIL, zope, ...)
>
> py3to2 can transparently import & mix & match 2.x & 3.0 scripts (but
> builtins/extensions must b 2.x - hence its a 2to3 migration tool).
Yes, I realize that, but there is another tool called 2to3 that
preforms syntax transformations on 2.x code. That's what the "2to3
conversion" tool component is for. |
|