Hi
I have my mezzanine project named as *mezzanine-test* and located at
/sites/test/code/mezzanine-test, inside *mezzanine-test* folder following
are the files.
ubuntu@test:/sites/test/code/mezzanine-test$ ls -l
total 156
drwxrwxr-x 3 ubuntu ubuntu 4096 Mar 17 19:27 *deploy*
-rwxr-xr-x
The project name needs to be a valid Python package name, which
mezzanine-test isn't since you can't use dashes.
Try mezzanine_test.
On Wed, Mar 19, 2014 at 2:04 PM, Ziwei Zhou ziweiz...@gmail.com wrote:
Hi
I have my mezzanine project named as *mezzanine-test* and located at
Thanks for the reply, now I got this error
ImportError: Could not import settings 'mezzanine_test.settings' (Is it on
sys.path? Is there an import error in the settings file?): No module named
'mezzanine_test'
On Wednesday, March 19, 2014 11:10:30 AM UTC+8, Stephen McDonald wrote:
The
yes, i renamed from mezzanine-test to mezzanine_test, but the error is the
same.
On Wednesday, March 19, 2014 11:58:14 AM UTC+8, Danny S wrote:
Did you also rename your directory?
Python can't handle dashes in module names, and your directory name
identifies the module as well.
On 19
In, your wsgi.py, you've got the following lines (which is fairly standard):
settings_module = %s.settings % PROJECT_ROOT.split(os.sep)[-1]
os.environ.setdefault(DJANGO_SETTINGS_MODULE, settings_module)
This will resolve to mezzanine_test.settings
Django will try to import this.
But as the
It certainly works. :) Just wondering when mezzanine makes the project
folder the same level as manage.py files, instead of following the
traditional django project format.
Thanks again.
On Wednesday, March 19, 2014 1:02:58 PM UTC+8, Danny S wrote:
In, your wsgi.py, you've got the
