What's the best practice for pip installing packages in the requirements section?

[Pav A]

Normally you get a warning that packages in the requirements section cannot be pip-installed.

What's the best practice for installing pypi packages that are not available on conda-forge, e.g. jupyter-cms?

At the moment I'm installing them using bld.sh/bat, but this defeats the purpose of using conda.

jupyter-cms requires post-install activation/registration, i.e. a post-build command. In my experience, post-link/pre-unlink scripts don't fire on Windows.

Any views would be appreciated.

[Chris Barker]

I take it you are trying ot build a conda package for a package that has a dependency that is  pip, but not in defaults or conda-forge?

In this case, I think the best solution is to make a conda package for the dependency as well.

ideally contribute that build to conda-forge. 

Alternatively, you _could_ pip install the dep in your build script -- that would then bundle it up with your package. This isn't as bad as it sounds, there is no real reason that a single conda package has to correspond to a single python package. But it would open the door to all sorts of confusion if anyone were to use your package and independently want to use the dep.

-CHB

--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+un...@continuum.io.
To post to this group, send email to co...@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/acd7faef-d3e4-4cf5-8b62-4609281f61fe%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris....@noaa.gov