it does with this change where it didn't before. At the very best you're still restarting the whole process instead of just wasting a bit of time

You should always catch ValueError when using int() on user input, because that input may not be a valid number.

I should also check to see if the length is reasonable, no? But the whole point of the issue is that nobody finds that practical.

Who uses a process per request for serving Python apps? That must be very uncommon. Even if you use a worker pool that isn’t going to restart a whole process just because of an errant exception in a request handler.

Also as noted if your whole process crashes because of errant input to int() you are beyond fucked in other ways.