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.
| Author | kaizhu |
|---|---|
| Recipients | benjamin.peterson, collinwinter, kaizhu, loewis, pitrou |
| Date | 2008年07月13日.19:01:57 |
| SpamBayes Score | 0.037265588 |
| Marked as misclassified | No |
| Message-id | <1215975787.47.0.0959957856132.issue3238@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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). @ the moment, every script compilable by py3to2 should b 3.0 language conformant, or otherwise it would fail the syntax check & byte-compile stage performed by the python 3.0 slave interpreter (see Mechanism for details). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月13日 19:03:07 | kaizhu | set | spambayes_score: 0.0372656 -> 0.037265588 recipients: + kaizhu, loewis, collinwinter, pitrou, benjamin.peterson |
| 2008年07月13日 19:03:07 | kaizhu | set | spambayes_score: 0.0372656 -> 0.0372656 messageid: <1215975787.47.0.0959957856132.issue3238@psf.upfronthosting.co.za> |
| 2008年07月13日 19:01:58 | kaizhu | link | issue3238 messages |
| 2008年07月13日 19:01:57 | kaizhu | create | |