Closed matthijskooijman closed 6 years ago
The use of a virtualenv is a prerequisite for djangocms-installer. Supporting other layouts in a multi-platform way has proven overly complex and unreliable and I have no plan to add it. Help welcome to support other layouts, as long as they don't break Windows support
With the changes proposed above, the installer seems to work (at least run without errors) in my environment, so that might be good to add. I'm not actually working with django-cms currently, so I can't provide more support than this, so if you want to close this, feel free.
@matthijskooijman thanks for the suggestion. after a few tests, it seems a sensible solution for your use case that does not breaks the other environments
Closed via #313
For some reason, the installer looks for
django-admin.py
in (only) the directory wherepython
is installed, which presumably works when python is installed using virtualenv and then pip installs django.However, when running a system-wide python from
/usr/bin
, with pip installations going into/usr/local/bin/
or~/.local/bin
, this fails to find django-admin.py:The code for this lives here: https://github.com/nephila/djangocms-installer/blob/develop/djangocms_installer/django/__init__.py#L45-L56
By changing this to, for example, the following, the current search is preserved and any file found is started using an explicit python call, but when no file is found there, the system PATH is used for a "django-admin.py" command instead.