Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #37575

Re: using split for a string : error

Date 2013-01-24 12:58 +0100
From "Tobias M." <tm@tobix.eu>
Subject Re: using split for a string : error
References <CAFqGZRGMXcku_nM_LqPsHpCzqGxF57LOSKwKwoCH+LyhPA8t_A@mail.gmail.com> <CAPTjJmpYi23Lx_4zuX28XURnAeaR-R=0w3e1mn6b0GBMs-O6Aw@mail.gmail.com> <51011822.3020702@tobix.eu> <CAPTjJmrqD7-x_sG_g-9YFFDanOct6_Grdw374EB69Kxy57LwLQ@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.972.1359028732.2939.python-list@python.org> (permalink)

Show all headers | View raw


Chris Angelico wrote:
> I'd not consider the performance, but the correctness. If you're
> expecting them to be integers, just cast them, and specifically
> _don't_ catch ValueError. Any non-integer value will then noisily
> abort the script. (It may be worth checking for blank first, though,
> depending on the data origin.)
Well, when I said you should catch the ValueError I didn't imply you 
should ignore the error and supress any error messages. Of course this 
depents on the use case. Maybe you want to raise another exception with 
a more user friendly error message or you might want to skip the line 
and just print a warning. :)

What I'm trying to say: When I give a script/program to a user who is 
not a python programmer I don't want him to see an error message like 
"ValueError: invalid literal for int() with base 10: 'abc'" as this 
would help him in no way.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: using split for a string : error "Tobias M." <tm@tobix.eu> - 2013-01-24 12:58 +0100

csiph-web