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 | Rhamphoryncus, benjamin.peterson, pitrou |
| Date | 2008年06月07日.05:33:43 |
| SpamBayes Score | 0.082447946 |
| Marked as misclassified | No |
| Message-id | <1212816827.93.0.567221219996.issue3021@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Ok, it makes sense to have the same behaviour for except and finally blocks then. As for the syntax error, I'm still not convinced. The point of Py3k is to change semantics: people should expect some incompatible changes. Also the previous behaviour was rather under-specified, so it could be considered a bug. And it seems to me syntax errors should be used to guard against potential syntax mistakes, not semantic subtleties. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月07日 05:33:49 | pitrou | set | spambayes_score: 0.0824479 -> 0.082447946 recipients: + pitrou, Rhamphoryncus, benjamin.peterson |
| 2008年06月07日 05:33:48 | pitrou | set | spambayes_score: 0.0824479 -> 0.0824479 messageid: <1212816827.93.0.567221219996.issue3021@psf.upfronthosting.co.za> |
| 2008年06月07日 05:33:46 | pitrou | link | issue3021 messages |
| 2008年06月07日 05:33:44 | pitrou | create | |