Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Igor Korot <ikorot01@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: Python Error message
Date: Thu, 4 Aug 2016 12:09:33 -0400
Lines: 73
Message-ID: <mailman.164.1470326982.6033.python-list@python.org>
References: <710599b6-b8c3-4f5a-a3dd-48757b816a44@googlegroups.com> <57a36593$0$1590$c3e8da3$5496439d@news.astraweb.com> <CA+FnnTw3b-iudGYJomeUYRQo_4ZathC7E1vWVqLDGqDo74JfDA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <57a36593$0$1590$c3e8da3$5496439d@news.astraweb.com>
Precedence: list
Xref: csiph.com comp.lang.python:112335

Steven,

On Thu, Aug 4, 2016 at 11:56 AM, Steven D'Aprano
<steve+python@pearwood.info> wrote:
> On Fri, 5 Aug 2016 01:31 am, GBANE FETIGUE wrote:
>
>> try:
>>   parsed_response =3D json.loads(response)
>>   deployid  =3D parsed_response[u'id']
>>   print "Your deployid is: " + deployid
>> except:
>>     print 'Seems the named id  already exists!'
>
>
> I'm not going to try to debug your code blindfolded with my hands tied
> behind my back. Get rid of those "try...except" blocks so that you can se=
e
> what error is *actually* happening.
>
> As you have it now, an error happens, somewhere. You don't know where the
> error is, or what it is, but Python generates a nice exception showing al=
l
> the detail you need to debug.
>
> But you catch that exception, throw it away, and then print a lie.
>
> It is **not true** that the named ID already exists. That is not what the
> error is, so why does your script tell a lie?
>
> The output from the server might give you a clue:
>
> "The server refused this request because the request entity is in a forma=
t
> not supported by the requested resource for the requested method."
>
>
> Never[1] use a bare "try...except". It is the worst thing you can do to a
> Python script, making it almost impossible to debug.
>
> https://realpython.com/blog/python/the-most-diabolical-python-antipattern=
/
>
> Fix that problem first, get rid of the "try...except" and lying print
> messages, and then either the bug will be obvious, or we can debug furthe=
r.
>
>
>
>
>
>
> [1] There are exceptions to this rule, for experts. But if you need to as=
k
> what they are, you're not ready to know

But even the experts will never write such a code - you never know what hap=
pens
in a month. Server might throw some new exception, you may move on to
a different project,
etc, etc. ;-)

Thank you.

>
>
> --
> Steve
> =E2=80=9CCheer up,=E2=80=9D they said, =E2=80=9Cthings could be worse.=E2=
=80=9D So I cheered up, and sure
> enough, things got worse.
>
> --
> https://mail.python.org/mailman/listinfo/python-list