Yeah could do
As this is the first time I have done testing or used pyenv I thought
perhaps I had made a mistake in my setup.
If you could just check this out.....
pip install --egg pyenv
sudo apt-get build-dep python2.7
pyenv install 2.7.9
pyenv virtualenv 2.7.9 py2.7.9-dj1.7
pyenv activate py2.7.9-dj1.7
pip install Django==1.7
pip install git+https://github.com/stephenmcd/mezzanine.git
pyenv activate py2.7.9-dj1.7
mezzanine-project mp-py2.7.9-dj1.7
cd mp-py2.79-dj1.7
python manage.py createdb --settings=settings
Thanks
G
On 06/04/15 14:15, Eduardo Rivas wrote:
Hmm, weird, as I'm testing out master with Django 1.7.7, and createdb
runs okay without the settings flag (only getting the test runner
warning). However, createdb fails with Django 1.8, but others have
noted that it has to do with some changes in the management command
API. May be worth to move this here:
https://groups.google.com/forum/#!topic/mezzanine-users/_QWfFVB3RVc
Are you creating the project with the "mezzanine-project" command?
Mezzanine currently uses a layout completely different to that of Django.
--
You received this message because you are subscribed to the Google
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
