Hi @psobolewskiPhD, added you as reviewer since you opened the original issue :)

Thanks @goanpeca!

the code that fetches the code still lives in napari

Is this something that should be revisited? (ie how hard would it be to pull this out too?)

Hi @jni

Is this something that should be revisited? (ie how hard would it be to pull this out too?)

Something to consider indeed, I think the only "user" of the file being modified in this PR is the napari-plugin-manager, so we could perhaps pull it out.

I think the only "user" of the file being modified in this PR is the napari-plugin-manager

And can we imagine any other users? To me it is indeed very weird that napari would contact conda-forge — to use the analogy motivating the original pull-out, it would be as if matplotlib was contacting conda-forge. That would be surprising!

To me it is indeed very weird that napari would contact conda-forge — to use the analogy motivating the original pull-out, it would be as if matplotlib was contacting conda-forge. That would be surprising!

Well technically we are pinging https://npe2api.vercel.app a napari maintained webservice, not conda-forge directly 🙃 .

And can we imagine any other users?

I cant think of any at the moment, but perhaps I need others to chime in here 🤔

Well technically we are pinging https://npe2api.vercel.app/ a napari maintained webservice, not conda-forge directly 🙃 .

Ah! Right! That's indeed a little different. I'm not sure but my instinct still says transplant it.

Without the plugin manager, can base napari do anything with the info it gathers from npe2api?
If not, then yeah it probably belongs in npe2 or in the manager.

Codecov Report

Attention: Patch coverage is 16.66667% with 10 lines in your changes are missing coverage. Please review.

Project coverage is 92.42%. Comparing base (2300b0e) to head (ab3dcc0).
Report is 3 commits behind head on main.

@@            Coverage Diff             @@
##             main    #6931      +/-   ##
==========================================
- Coverage   92.48%   92.42%   -0.06%     
==========================================
  Files         612      612              
  Lines       55165    55171       +6     
==========================================
- Hits        51018    50991      -27     
- Misses       4147     4180      +33     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Did a quick search for usage of npe2api module, and indeed it does not seem to be used anywhere inside napari.

Without the plugin manager, can base napari do anything with the info it gathers from npe2api?

nope at the moment :)

Now in the spirit of making less PRs, any chance we could get this merged here 🙈 so I can then proceed to transplant it?

Now in the spirit of making less PRs, any chance we could get this merged here 🙈 so I can then proceed to transplant it?

Seems reasonable to me. Fix it, then port it over.

Any suggestions on the current text I used are welcome:

There seems to be an issue with network connectivity. Remote plugins cannot be installed, only local ones.

I took it loosely from what @psobolewskiPhD wrote on the original issue, but perhaps it could be made more clear/concise :)

Created this napari/napari-plugin-manager#33 to track "transplants"

Thanks @jni!

Working on the transplant now :)