[Python-Dev] syntax misfeature (exception) (original) (raw)
Phillip J. Eby pje at telecommunity.com
Sun Jan 21 15:12:54 CET 2007
- Previous message: [Python-Dev] syntax misfeature (exception)
- Next message: [Python-Dev] syntax misfeature (exception)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 01:17 PM 1/20/2007, Josiah Carlson wrote:
Neal Becker <ndbecker2 at gmail.com> wrote: [snip] > It's not a question, it's a critique. I believe this is a misfeature since > it's so easy to make this mistake.
And it is going away with Py3k. Making it go away for Python 2.6 would either allow for two syntaxes to do the same thing, or would require everyone to change their except clauses. Neither is very desireable (especially if writing code for 2.6 makes it not work for 2.5).
With both, you can choose whether you'd rather your code be backward compatible with 2.5, or forward-compatible with 3.0. So 2.6 has to have both syntaxes.
- Josiah
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/pje%40telecommunity.com
- Previous message: [Python-Dev] syntax misfeature (exception)
- Next message: [Python-Dev] syntax misfeature (exception)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]