Menu
When I Install a venv and install Django in it for example "DjangoUpgrade" then I am missing at this path the templates folder
:~/.venvs/DjangoUpgrade/local/lib/python2.7/site-packages/django/contrib/admin
Just to be clear this is the ls from that folder.
actions.py exceptions.py filters.py forms.py helpers.py __init__.py models.py options.py sites.py templatetags tests.pyc util.pyc validation.pyc widgets.py
actions.pyc exceptions.pyc filters.pyc forms.pyc helpers.pyc __init__.pyc models.pyc options.pyc sites.pyc tests.py util.py validation.py views widgets.pyc
This happens at Django 1.3 / 1.4 in completely fresh venvs, both when nothing else is installed yet and when everything else is installed fine via pip.
When I copy the admin templates folder from a working colleagues correct install it works then perfectly. What is going wrong here?
[We're upgrading through the versions atm so forgive the older Django version, it's still supported though]
python 2.7.3. Django 1.4.20 pip 7.0.3
853
The default templates used by the Django admin are located under the /django/contrib/admin/templates/ directory of your Django installation inside your operating system's or virtual env Python environment (e.g. <virtual_env_directory>/lib/python3. 5/site-packages/django/contrib/admin/templates/ ).
To view the default admin template you can access it in the django/contrib/admin/templates/admin folder. In this situation you will most likely be using a virtual environment and can find this folder in the directory that contains all the installed libraries.
Run django-admin help to display usage information and a list of the commands provided by each application. Run django-admin help --commands to display a list of all available commands. Run django-admin help <command> to display a description of the given command and a list of its available options.
Using virtualenv to install Django is recommended on DreamHost Shared and Private servers since your user doesn't have access to install into shared directories. When you use virtualenv, you create an isolated environment with its own installation directories which your user has full permissions to.
To solve this issue you should use "--no-binary" while installing django.
pip install --no-binary django -r requirements.txt
or
pip install --no-binary django django==1.4.21
Remember to upgrade your PIP installation to have the "--no-binary" option.
You can get further information in this link: https://github.com/pypa/pip/issues/2823
109
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
