On Tue, 7 May 2024 at 03:42, jak via Python-list wrote:
>
> Loris Bennett ha scritto:
> > r...@zedat.fu-berlin.de (Stefan Ram) writes:
> >
> >>Me (indented by 2) and the chatbot (flush left). Lines lengths > 72!
> >
> > Is there a name for this kind of indentation, i.e. the stuff you are
> >
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
Loris Bennett ha scritto:
r...@zedat.fu-berlin.de (Stefan Ram) writes:
Me (indented by 2) and the chatbot (flush left). Lines lengths > 72!
Is there a name for this kind of indentation, i.e. the stuff you are
writing not being flush left? It is sort of contrary to
what I think of as
Stefan Ram ha scritto:
r...@zedat.fu-berlin.de (Stefan Ram) wrote or quoted:
translation services are gonna interpret line breaks as
I just beefed up my posting program to replace "gonna".
Now I won't come across like some street thug, but rather
as a respectable member of human
From a practical perspective: not all values are printable (especially
if printing a value results in an error: then you'd lose the original
error, so, going crazy with printing of errors is usually not such a
hot idea).
But, if you want the values: you'd have to examine the stack, extract
the
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:
>
>
