@Rosuav No. You could have a good name to give the function if you had to, yet believe that code understandability alone doesn’t make it necessary or relevent to separate the function from the rest. In such a situation, a function like select_which_moon_or_satellite_to_go_to would only be defined because the syntax gives no other choice. Even though we have a good name available for it.
And the more I think about it the more I come to disagree with the concession I made in my previous message : if you want to name a code snippet that you only use once, you should probably just put a comment before it. I’m not judging anyone’s practices, but I personally would probably never define a function just for that.
If you want more context for the example I imagined just then, say I want to select a moon from several star systems :
for system in systems:
for planet in system:
for moon in planet.moons:
if moon.has_no_titanium:
break 2 # I don't want to be in a system with a moon with no titanium
if moon.has_atmosphere:
break # I don't want to be in the same planetary system