Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
Hi Odhiambo,
Am 28.03.12 17:13, schrieb Odhiambo Washington:
Hey Jeff and all,
I followed the "five minute guide", but I am hitting a brickwall:
[root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# python manage.py syncdb Traceback (most recent call last): File "manage.py", line 29, in <module> execute_manager(settings) File "/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py", line 459, in execute_manager utility.execute() File "/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/backends/dummy/base.py", line 15, in complain raise ImproperlyConfigured("settings.DATABASES is improperly configured. " django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details.
You're doing nothing wrong! Except you're using the latest Django version (1.4) which was released only some days ago... :-)
In Django 1.2 support for multiple databases has been added, so they extended the format of the db definition in settings.py. It looks like in 1.4 the old format (which we have used so far) is no longer supported which most definitely causes the above error to be thrown.
Changing the DATABASE setting in dev_setup/settings.py should do the trick. Like here: https://docs.djangoproject.com/en/1.4/ref/settings/#databases
I will fix that in our launchpad branch as well, so these changes will go into the next alpha (which will probably be released not too far from now... :-)
Florian
Can anyone tell what I am doing wrong?
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind....
Security Policy: http://wiki.list.org/x/QIA9
On Wed, Mar 28, 2012 at 19:13, Florian Fuchs <f@state-of-mind.de> wrote:
Hi Odhiambo,
Hey Jeff and all,
I followed the "five minute guide", but I am hitting a brickwall:
[root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup#
Am 28.03.12 17:13, schrieb Odhiambo Washington: python
manage.py syncdb Traceback (most recent call last): File "manage.py", line 29, in <module> execute_manager(settings) File
"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py",
line 459, in execute_manager utility.execute() File
"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py",
line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File
"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py",
line 196, in run_from_argv self.execute(*args, **options.__dict__) File
"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py",
line 232, in execute output = self.handle(*args, **options) File
"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py",
line 371, in handle return self.handle_noargs(**options) File
"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/commands/syncdb.py",
line 57, in handle_noargs cursor = connection.cursor() File
"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/backends/dummy/base.py",
line 15, in complain raise ImproperlyConfigured("settings.DATABASES is improperly configured. " django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details.
You're doing nothing wrong! Except you're using the latest Django version (1.4) which was released only some days ago... :-)
In Django 1.2 support for multiple databases has been added, so they extended the format of the db definition in settings.py. It looks like in 1.4 the old format (which we have used so far) is no longer supported which most definitely causes the above error to be thrown.
Changing the DATABASE setting in dev_setup/settings.py should do the trick. Like here: https://docs.djangoproject.com/en/1.4/ref/settings/#databases
I will fix that in our launchpad branch as well, so these changes will go into the next alpha (which will probably be released not too far from now... :-)
Florian
Can anyone tell what I am doing wrong?
Hi Florian,
Thanks for that.
Thata fixed my issue:
[root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# python manage.py syncdb Creating tables ... Creating table auth_permission Creating table auth_group_permissions Creating table auth_group Creating table auth_user_user_permissions Creating table auth_user_groups Creating table auth_user Creating table django_content_type Creating table django_session Creating table django_site Creating table django_admin_log Creating table social_auth_usersocialauth Creating table social_auth_nonce Creating table social_auth_association
You just installed Django's auth system, which means you don't have any superusers defined. Would you like to create one now? (yes/no): yes Username (leave blank to use 'root'): admin E-mail address: odhiambo@gmail.com Password: Password (again): Superuser created successfully. Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s)
However, I am lost as to why the argument to this procedure was named "syncdb" and not "createdb", which is what it's doing. Can you explain that please? Sorry, I am a noob in this.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.
participants (2)
-
Florian Fuchs -
Odhiambo Washington