-
Notifications
You must be signed in to change notification settings - Fork 12
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
conda environment generated from requirements.txt is not completely functional #97
Comments
If you find any packaing problems with https://github.com/conda-forge/django-ajax-selects-feedstock/issues Maybe it just needs the right version? |
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
looks like I need to spceify the channel, but what is the channel? I tried ODM2 but that yielded the same result. |
Also I've actually been using python 2.7.12 in the environment running the application. |
You can do like we what we have in the 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:
The former will add |
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. |
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. |
When attempting to run ODM2 Admin with a conda environment generated from requirement.txt some errors are encountered:
inline forms were not rendering, I'm guessing this has to do with this import not working properly https://github.com/miguelcleon/ODM2-Admin/blob/master/odm2admin/forms.py#L2
ajax lookup fields sometimes weren't working. I haven't been able to figure out why some worked and others did not.
@ocefpaf probably there is some problem with django-ajax-selects?
@lsetiawan maybe you could see if you can replicate the problems?
The text was updated successfully, but these errors were encountered: