-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Napari Bundled App [Mac ARM build] interface bug #145
Comments
Could you clarify that you are referring to the If so, the lack of napari-skimage is likely due to the fact that the bundled app installs from conda-forge and not pypi. So until that plugin is on conda-forge it will not be installable in the bundled app via the GUI. I am puzzled why the path option is gone, this could be also related to the use of conda for installing. |
@jaimergp is the lack of the |
Yes indeed that's what I refer to.
Is there no way to install from Pypi with the bundled app?
Thanks! |
There is no supported way. |
I am just using the python version now. But if the plugins can't be installed in bundled version, I find it really restricts the use case of that. |
All plugins that have version on conda forge could be installed in bundled version. |
I'm hoping that with
Let me ping @goanpeca for this, because I'm not sure. 0.4.19 didn't use Let me take a look at the nightly pipelines so we can test the artifacts. osx-64 has been failing for a few weeks, apparently. |
Ah wait, it's here https://github.com/napari/napari/releases/tag/latest |
New artifacts as of today in https://github.com/napari/napari/actions/runs/9409516454 |
🐛 Bug Report
I used the latest available build [0.4.19]. The Install by name/url field is missing in the build, whereas if I install with python it is showing.
But the main reason I was looking for that field was due to not being able to install napari-skimage.
This problem only exists in the app.
💡 Steps to Reproduce
Reproducible by opening the Install/Uninstall plugins window.
💡 Expected Behavior
No response
🌎 Environment
💡 Additional Context
No response
The text was updated successfully, but these errors were encountered: