Package Request: uwsgi

[prince-mishra]

Not sure if this is the correct location for package requests, but can we please get uwsgi in defaults?

Since this package was not available on the defaults channel, I tried to install it using pip, which was successful, but this creates problems when the same package is installed in a separate environment and the previous environment is deleted.

Steps to reproduce:

$ conda create -yn env1 python pip pcre
$ source activate env1
$ pip install uwsgi # This downloads the tarball, builds it and keeps it in cache
$ uwsgi --help # Works!
# ... Something bad happens in env1, I wanna nuke it.
$ conda create -yn env2 python pip
$ source activate env2
$ conda env remove -yn env1
$ pip install uwsgi # This picks up the cached, already built stuff
$ uwsgi --help
uwsgi: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory
$ chrpath -l `which uwsgi`
/path/to/env2/bin/uwsgi: RPATH=/path/to/env1/lib
# But I deleted env1 !!

This problem goes away if I use: pip install --no-cache-dir for all pip packages. However, I wanted to leverage the use of conda env create -f /path/to/env.yaml, which seems to honor the cache. Is there an option to tell pip to not use cache while creating a new environment using a env.yml?

[nehaljwani]

I've been bitten by this many times in the past. It's a major support headache.

@kalefranz Should we fix this by adding --no-cache-dir to

https://github.com/conda/conda/blob/4.3.x/conda_env/installers/pip.py#L8 (4.3.x) or https://github.com/conda/conda/blob/4.4.x/conda_env/installers/pip.py#L40 (4.4.x)

and optionally, make it controllable via a CLI parameter?

[kalefranz]

See https://github.com/conda/conda/pull/3969, which is merged into 4.4.x.

Sounds like the root cause of the problem here relates to https://github.com/conda/conda/issues/6079. The network of issues linked off that is also an interesting read.

[kalefranz]

I know conda-forge has a uwsgi package. I know because it's one I contributed.