conda environment generated from requirements.txt is not completely functional about cz-manager

[miguelcleon]

Ok, great. I've been able to reproduce the problem. I was using an older version of django-ajax-selects. The solution should be to fix the bug rather then pin the package. I'll open another issue with the details.

[ocefpaf]

@ocefpaf probably there is some problem with django-ajax-selects?

If you find any packaing problems with django-ajax-selects selects let me know in:

https://github.com/conda-forge/django-ajax-selects-feedstock/issues

Maybe it just needs the right version?

[miguelcleon]

So I thought I'd test this by creating the environment again and inspecting the django-ajax-selects version in the environment I'm using to run the application and a fresh environment generated from the requirements.txt file. However when I run conda create --yes -n ENVNAME python=3.5 --file requirements.txt I get `PackageNotFoundError: Package not found: '' Packages missing in current linux-64 channels:

• django-admin-shortcuts
• django-ajax-selects
• django-apptemplates
• django-daterange-filter
• django-import-export
• django-jquery
• djangocms-admin-style==0.2.7
• django-recaptcha`

looks like I need to spceify the channel, but what is the channel? I tried ODM2 but that yielded the same result.

[miguelcleon]

Also I've actually been using python 2.7.12 in the environment running the application.

[ocefpaf]

You can do like we what we have in the .travis.yml file:

conda config --add channels conda-forge --force
conda create -n ENVNAME python=2.7 --file requirements.txt --file requirements-dev.txt

or you can do all in one command with:

conda create -n ENVNAME python=2.7 --file requirements.txt --file requirements-dev.txt -c conda-forge

The former will add conda-forge to your .condarc file the latter won't.

[miguelcleon]

Ok, I'm still getting the other problem I had noticed. This isn't as big of a problem but it still should to be addressed. I'll open another issue for that.