Open k-dominik opened 2 years ago
I was following the installation instructions in the Readme, but got the following error first of all I was wondering why at all anything happens outside conda? I don't want to do anything in
/usr/local/...
Thanks for spotting the issue! The problem is the missing pip
dependency in lockfiles, therefore, system-wide pip will be used (or whatever version you had in your current PATH
). I'll add pip
to lockfiles, and change pip
to python -m pip
in README
, which is the recommended practice from people close to Python development.
also it would be nice to have a conda-only solution for installation.
This plugin is supposed to be available through pip because napari searches plugins in PyPI. Unfortunately, fastfilters
is a conda-only dependency, but I was planning to replace it with the new Halide-based implementation. Of course, adding a conda package on top of that would be nice too.
Also when I go the conda route, (guessing dependencies) I get
This is expected if you did not install this package, because napari's plugin system works by examining packages' entry points, specified through distutils
or setuptools
in setup.cfg
or setup.py
.
only plugin discovery (as in downloadable from within napari) goes via pypi (does only matter if the plugin is actually on there - no installation instructions needed). Plugin execution should still work from a conda environment (locally "installed" plugins can be run afaik). Hence it would be great to have a conda only - as in no pip involved - way to install a dev env for this plugin.
edit: entry points can be set in meta.yaml
Hello,
I was following the installation instructions in the Readme, but got the following error
first of all I was wondering why at all anything happens outside conda? I don't want to do anything in
/usr/local/...
also it would be nice to have a conda-only solution for installation.
Also when I go the conda route, (guessing dependencies) I get