GeezerVison

I would have really preferred something like threading.iterate to mimick the way we name things, e.g., enumerate[this], iter[over that], filter[this], map[it], etc (all of them are verbs), but I see why it's named iter_locked to mimick iter, though it looks like a variable name to me rather than a function name. My rationale for not having locked inside the name is that it belongs to the threading module, and thus semantically should be used by something that is threading-related, but this is probably too many guesses

I'm still not a huge fan of putting this in threading. threading should be for synchronization primitives, but this is a utility.

Just an idea: what about using the builtin iter with a new keyword locked? For locked=False we have the normal behavior, for True we use the iter_locked defined here.

I like that idea, but it would require a lot more work to accomplish. Changes to builtins require PEPs.

This PR is stale because it has been open for 30 days with no activity.

#148894 is a more complete implementation, closing this PR

#148894 is a more complete implementation, closing this PR

You didn't close the PR. I suppose that it was a mistake, so I close the PR.