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 | pitrou |
|---|---|
| Recipients | collinwinter, kaizhu, loewis, pitrou |
| Date | 2008年06月30日.14:27:45 |
| SpamBayes Score | 0.02337301 |
| Marked as misclassified | No |
| Message-id | <1214836125.38.0.183235775311.issue3238@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Some remarks: - I don't think doing a bulk backport of ceval.c is the right approach. Instead, each functionality should be considered and backported independently, if desired. - Guido already said that 3.0 should be mostly clean from compatibility-related code, so forward-porting 2.x opcodes is out of the question. There's a reason they removed in the first place :-) - Some functionalities shouldn't be backported, e.g. introducing SETUP_EXCEPT was motivated by the different semantics of exception cleanup in py3k, backporting it would probably break some 2.x code. - Compatibility between the two eval loops (2.x and py3k) is probably the tip of the iceberg. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月30日 14:28:45 | pitrou | set | spambayes_score: 0.023373 -> 0.02337301 recipients: + pitrou, loewis, collinwinter, kaizhu |
| 2008年06月30日 14:28:45 | pitrou | set | spambayes_score: 0.023373 -> 0.023373 messageid: <1214836125.38.0.183235775311.issue3238@psf.upfronthosting.co.za> |
| 2008年06月30日 14:27:47 | pitrou | link | issue3238 messages |
| 2008年06月30日 14:27:46 | pitrou | create | |