On Tue, 7 May 2024 at 03:38, Alan Bawden via Python-list
wrote:
> A good error message shouldn't withhold any information that can
> _easily_ be included. Debugging is more art than science, so there is
> no real way to predict what information might prove useful in solving
> the crime. I
etc.) It's tedious and prone to
errors. So, if you really want to do this automatically for every
error that's going to be quite a bit of work.
On Fri, May 3, 2024 at 6:58 PM Johanne Fairchild via Python-list
wrote:
>
> How to discover what values produced an exception? Or perhaps---why
>
Thomas Passin writes:
On 5/3/2024 9:56 AM, Johanne Fairchild via Python-list wrote:
> How to discover what values produced an exception? Or perhaps---why
> doesn't the Python traceback show the values involved in the TypeError?
> For instance:
&
On 2024-05-03 at 10:56:39 -0300,
Johanne Fairchild via Python-list wrote:
> How to discover what values produced an exception? Or perhaps---why
> doesn't the Python traceback show the values involved in the TypeError?
> For instance:
Johanne Fairchild wrote at 2024-5-3 10:56 -0300:
>How to discover what values produced an exception? Or perhaps---why
>doesn't the Python traceback show the values involved in the TypeError?
>For instance:
>
>--8<&g
On 5/3/2024 9:56 AM, Johanne Fairchild via Python-list wrote:
How to discover what values produced an exception? Or perhaps---why
doesn't the Python traceback show the values involved in the TypeError?
For instance:
--8<>8---
(0,
How to discover what values produced an exception? Or perhaps---why
doesn't the Python traceback show the values involved in the TypeError?
For instance:
--8<>8---
>>> (0,0) < 4
Traceback (most recent call last):
