Can you post your full code somewhere as a zip?
On Thu, Apr 12, 2012 at 2:33 PM, Leonid Toshchev <ltoshc...@gmail.com>wrote:
> Hello.
> Try to escape spaces. I don`t check how django work when path have
> spaces inside, but i meet same problems in my practice.
>
> p.s. sorry for my bad english.
>
> 12 апреля 2012 г. 21:32 пользователь victoria <ka...@bitnami.org> написал:
> > On Thu, Apr 12, 2012 at 7:09 PM, Brandy <brandy.norri...@yahoo.com>
> wrote:
> >> I am working (again) through the tutorial part 1. I have made changes to
> >> Engine and Name as specified in the instructions. However, running
> "python
> >> manage.py syncdb" continues to return "Please supply the ENGINE value."
> I
> >> did not encounter this problem the first time I worked through this
> >> tutorial.
> >>
> >> # Django settings for mysite project.
> >>
> >> DEBUG = True
> >> TEMPLATE_DEBUG = DEBUG
> >>
> >> ADMINS = (
> >> # ('Your Name', 'your_em...@example.com'),
> >> )
> >>
> >> MANAGERS = ADMINS
> >>
> >> DATABASES = {
> >> 'default': {
> >> 'ENGINE': 'django.db.backends.sqlite3', # Add
> 'postgresql_psycopg2',
> >> 'mysql', 'sqlite3' or 'oracle'.
> >> 'NAME': 'c:/program files/bitnami
> >> djangostack/mysite/sqlite3.db', # Or path to
> database
> >> file if using sqlite3.
> >> 'USER': '', # Not used with sqlite3.
> >> 'PASSWORD': '', # Not used with sqlite3.
> >> 'HOST': '', # Set to empty string for
> >> localhost. Not used with sqlite3.
> >> 'PORT': '', # Set to empty string for
> default.
> >> Not used with sqlite3.
> >> }
> >> }
> >>
> >
> > Your settings seem correct. Which version of django are you using?
> > Have you checked that the settings.py file is in the correct location
> > for your django version?
> >
> > Django 1.4 expects this layout:
> >
> > mysite/
> > manage.py
> > mysite/
> > __init__.py
> > settings.py
> > urls.py
> > wsgi.py
> >
> > While Django 1.3 expects this:
> >
> > mysite/
> > __init__.py
> > manage.py
> > settings.py
> > urls.py
> >
> >
> > Since 1.4 was released this seems one of the most common mistakes that
> > could cause this error.
> >
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Django users" group.
> >> To view this discussion on the web visit
> >> https://groups.google.com/d/msg/django-users/-/qnfmdfEObKAJ.
> >> To post to this group, send email to django-users@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> django-users+unsubscr...@googlegroups.com.
> >> For more options, visit this group at
> >> http://groups.google.com/group/django-users?hl=en.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django users" group.
> > To post to this group, send email to django-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
