-
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
Pydantic error when launching napari via installed constructor bundle #80
Comments
Yes, we need to regenerate the installers to accommodate the new version constraints. I am waiting for a couple PRs to be merged, but should be ready this week. I'll let you know when they are available! |
Awesome @jaimergp, the new bundle works nicely on my machine. It also made a I was also able to install the napari-imagej plugin using the graphical plugin installer. But when OpenJDK spins up, it crashes. 😭 But on the napari packaging side, this issue is definitely resolved! 👍 |
Do you have an error message for the OpenJDK error? You should be able to launch napari from its internal conda environment (somewhere in ~/.local). |
@jaimergp It's a SIGSEGV. If you're interested in digging, the issue is at imagej/napari-imagej#269. |
I installed the napari-0.4.18 Linux constructor bundle. When I try to run the installed napari-0.4.18 directly, here's what I see:
The napari 0.4.18 I have installed into a regular conda environment (not via the constructor installer) launches successfully.
It seems pretty clear that the problem is that the constructor bundle installs pydantic 2, whereas napari still works with pydantic 1:
But I could paste a more complete diff of my two environments if that would be helpful.
The text was updated successfully, but these errors were encountered: