Duplicate function `find_connection_file` with similar API to one in `jupyter_client` about ipykernel HOT 3 CLOSED

I think the ipykernel one might have a (slightly) different behavior for historical reasons (it will look in .ipython). You can see that as the the ipykernel does even call the jupyter_client one at the end.

I don't see any obvious reason not to deprecate it slowly, or at least warn not to use it.
I doubt we can completely remove it, but it can likely become a private method at some point.

from ipykernel.

Yeah, I think it is only slightly different in the path it uses. It's a good idea for one or the other to get a new name, just so it's clearer when one is used instead of the other (I can almost guarantee that in doing so we will find at least one case where we are using the wrong one).

from ipykernel.

Actually, turns out we don't really use this one for anything. We can just deprecate it.

from ipykernel.