At 01:17 PM 1/20/2007, Josiah Carlson wrote:
Neal Becker [EMAIL PROTECTED] 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
Phillip J. Eby [EMAIL PROTECTED] wrote:
At 01:17 PM 1/20/2007, Josiah Carlson wrote:
Neal Becker [EMAIL PROTECTED] 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.
I accidentally wrote:
try:
...
except a,b:
rather than:
try
...
except (a,b):
It appears that the 1st example syntax is silently accepted, but doesn't
seem to work. Is this true? If so, I'd say it's a wart.
___
Python-Dev mailing list
Neal Becker schrieb:
I accidentally wrote:
try:
...
except a,b:
rather than:
try
...
except (a,b):
It appears that the 1st example syntax is silently accepted, but doesn't
seem to work. Is this true? If so, I'd say it's a wart.
Both have a meaning: The first assigns the
Georg Brandl wrote:
Neal Becker schrieb:
I accidentally wrote:
try:
...
except a,b:
rather than:
try
...
except (a,b):
It appears that the 1st example syntax is silently accepted, but doesn't
seem to work. Is this true? If so, I'd say it's a wart.
Both have a meaning:
Neal Becker [EMAIL PROTECTED] 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
On Sunday 21 January 2007 05:17, Josiah Carlson wrote:
Neal Becker [EMAIL PROTECTED] 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
