CLN: tighten Exception catching in indexing.py
get rid of is_lexsorted_for_tuple while we're at it
Are exceptions simply being handled more specifically now?

Or are they be handled higher up in the stack now? Echoing @gfyoung's question, it would be helpful if you add some explanation why you are removing / changing things in your PRs. lgtm.  > Are exceptions simply being handled more specifically now?  Or are they be handled higher up in the stack now?

They are no longer reached.  AFAICT this is leftover from Panel indexing can you add a whatsnew note, technically this *was* public api; ping on green. ping