Paul,
I think you are fixating too much on Ken's example. I think I understand
what he
is saying and I agree with him. It is a problem I struggle with routinely. It
occurs in
the following situations:
1. You are handling an exception that you are not raising. This could be because
Pyth
we are now.
And frankly, I don't see any downside. The changes he is proposing are
tiny and simple and backward compatible.
-Jeff
03.07.2017, 14:23, "Paul Moore" :
> On 3 July 2017 at 20:46, Jeff Walker wrote:
>> I think you are fixating too much on Ken's ex
I am one of those that also find you to be too negative. I find your critiques
to
be useful. You often raise issues that had not occurred to me. But then you
go further an make pronouncements which I think go too far. For example:
> the idea doesn't actually solve the problem it is intended to
o
Stephen,
These statements do not ring true to me. I have been following the
conversation
closely and I have not seen support for any of them. Perhaps I missed it.
Could you please expand on these statements:
> the idea doesn't actually solve the problem it is intended to
Specifically Ken st
Paul,
I am having trouble understanding your response.
06.07.2017, 03:58, "Paul Moore" :
> On 6 July 2017 at 02:53, Jeff Walker wrote:
>> Could you please expand on these statements:
>>
>>> the idea doesn't actually solve the problem it is intende
06.07.2017, 13:00, "Steven D'Aprano" :
> What prevents the programmer from writing this?
>
> raise NameError(nym=s, template="name '{nym}' is not defined.")
>
> Or any other keyword name for that matter. Since the exception class
> accepts arbitrary keyword arguments, we have to expect that it coul
Sorry Stephen (and Steven). I'll do better next time.
The way I see it there are two problems, and the second causes the first.
The first problem is that there is no direct access to the components that make
up the error in some of the standard Python exceptions.
>>> foo
Traceback (most
15.07.2017, 18:33, "Chris Angelico" :
> On Sun, Jul 16, 2017 at 10:12 AM, Jeff Walker
> wrote:
>> The first problem is that there is no direct access to the components that
>> make up the error in some of the standard Python exceptions.
>>
>> >
