Hi,
> def get_html(...):
> try:
> ... actually go get the info
> return info
> except (ConnectionError, OSError, SocketError) as e:
> raise ContentNotFoundError from e
Personally, I never liked "early returns". I would rather used a variable and
the last line in t
Hi,
You are right. I am trying to address a few questions at the same time.
As English is not my first language, I can only say that you have addressed
them very well. Thanks.
1. Where to put the try/except block, inside or outside the function
2. How to deal with un-anticipated exceptions
3.
Hi,
If I may, I feel you are tying to address a few questions at the same time,
although they are related
1. Where to put the try/except block, inside or outside the function
2. How to deal with un-anticipated exceptions
3. How to keep record
My personal feelings are:
1. Kind of prefer try/except
在 2015年11月4日星期三 UTC-6下午10:18:33，zlju...@gmail.com写道：
> > Which would you prefer?
>
> So if I am just checking for the ConnectionError in get_html and a new
> exception arises, I will have traceback to the get_html function showing that
> unhandled exception has happened.
> Now I have to put addi
On Thu, Nov 5, 2015 at 3:18 PM, wrote:
>> Which would you prefer?
>
> So if I am just checking for the ConnectionError in get_html and a new
> exception arises, I will have traceback to the get_html function showing that
> unhandled exception has happened.
> Now I have to put additional excepti
> Which would you prefer?
So if I am just checking for the ConnectionError in get_html and a new
exception arises, I will have traceback to the get_html function showing that
unhandled exception has happened.
Now I have to put additional exception block for managing the new exception in
the get
On Monday, 2 November 2015 21:59:45 UTC+1, Ian wrote:
> I'm having a hard time understanding what question you're asking.
:)
I am really having a hard time to explain the problem as English is not my
first language.
> You
> have a lot of discussion about where to handle exceptions,
That's
On Thu, Nov 5, 2015 at 2:41 PM, wrote:
> Raising an exception forces me to put every call of the get_html function in
> try/except block.
> If I am returning a special value, than I can call get_html and then test the
> value.
>
> I am not sure which approach is better.
Raising an exception me
> The best way is probably to do nothing at all, and let the caller handle
> any exceptions.
In that case every call of the get_html function has to be in the try/except
block with many exceptions.
Sometimes, it is enough just to know whether I managed to get the html or not.
In that case, I coul
On Mon, Nov 2, 2015 at 12:24 PM, wrote:
> I have read some articles that returning None is not a good approach, so I am
> confused.
>
> How to handle exceptions properly in a pythonic way?
I'm having a hard time understanding what question you're asking. You
have a l
In <4b303213-62e2-42d4-b2f6-4fc1f6025...@googlegroups.com> zljubi...@gmail.com
writes:
> Let's say that I have the following simple function:
> def get_html(url):
> wpage = requests.get(url)
>
> return wpage.text
> How to handle exceptions properly that can arise during execution
e. Caller doesn't need try/except block anymore. Something like this:
if get_html('www.abc.com/index.html') is not None:
I_am_sure_that_html_has_been_downloaded_correctly
Now if I want to catch a new exception, I can catch it in get_html function,
which is the only change in the program.
I
12 matches
Mail list logo
