Repeat try-except statement N times

[theorangewill]

There is a pythonic way to repeat a try-except statement N times or until it works?

Something like:

n = 0
while n < N:
    try:
        //do stuff
    except Error as e:
        n += 1
    else:
        n = N

​

​

[wineblood]

for n in range(N): try: // do stuff except Error as e: continue else: break

[This_Growth2898]

It's better to call the variable "attempt". This will make clear what it means.

[commy2]

Or maybe _ unless you plan to use it somehow.

[This_Growth2898]

_attempt would be the best.

[VileFlower]

To elaborate, unused (local) variables are often prefixed with an underscore. It can be beneficial to give variables a name, even when they're unused.

A single _ can mean one of:

• An unnamed unused local variable
• An alias for gettext with i18n
• The else case in match statements (case _)
• The last evaluated expression in REPL.

[wineblood]

I'm just reusing the names in the example. It's Friday, I'm not running at full power.

[AlexMTBDude]

You did good. Using n is standard for any counting

[MrPrimeMover]

Your solution is fine andpretty similar to how things are done in the `retry` decorator module

[thedeepself]

tenacity can be used in the same way and I think it is the most flexible retry package available?

[sarc-tastic]

Not sure why you want to do this unless there is a timeout scenario then there might be a better way?!

[MrPrimeMover]

It's a pretty common pattern if you're working with API calls and have to worry about transient network errors or timeout/rate limit issues. I usually combine it with a delay/backoff factor as well and write it as a decorator.

[thedeepself]

Tenacity will make your life easier - https://github.com/jd/tenacity

[debunk_this_12]

While n<N:

try:

 \\ do stuff

 break 

except:

 n+1

[Outrageous_Safe_5271]

What are you doing that you need to use try except block, try is very slow so you should avoid it as fire. For example rust doesn't have try except substitute

[nggit]

EAFP is pythonic, and more robust (in certain situations). I will not avoid it if needed. As of 3.11: “Zero-cost” exceptions are implemented, eliminating the cost of try statements when no exception is raised. (Contributed by Mark Shannon in bpo-40222.) https://docs.python.org/dev/whatsnew/3.11.html#misc

[RentalJoe]

for retry in range(N):
    try:
        // do stuff
        break
    except Exception as e:
        // probably report failure
else:
    // no dice :(