Move the try outside the loop when this is possible in Airflow core

[hussein-awala]

All the blocks with this pattern

while/for:
try:
...
except:
return/break/raise

could be refactored to

try:
while/for:
...
except:
return/pass/raise

Why?

To make the code more readable and fatser:

importtimeitcode1="""try: for i in range(100000): if i == 99999: raise Exception("test")except Exception as e: pass"""code2="""for i in range(100000): try: if i == 99999: raise Exception("test") except Exception as e: pass"""time_taken_code1=timeit.timeit(stmt=code1, number=1000, globals=globals())
time_taken_code2=timeit.timeit(stmt=code2, number=1000, globals=globals())
print("Time taken by loop in try:", time_taken_code1)
print("Time taken by try in loop:", time_taken_code2)

and here is the result:

$ python try_except_loop.py Time taken by loop in try: 2.8077976499916986
Time taken by try in loop: 3.2557358630001545

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[uranusjr]

While we are at this, I wonder if we should remove this exception wrapping. It doesn’t have any value from what I can tell. Same for the one in __init__.py.

[hussein-awala]

I had the same question because it seems useless. However I prefer to keep this PR changing the syntax without any change in the functionality, I will open some new PR to improve the raised exceptions.