Ok it looks like there is an issue with my desktop. I did everything
from scratch on my labtop (also running opensuse) and changes to the
settings file now work

On Feb 17, 9:05 pm, Detectedstealth <[email protected]> wrote:
> I am starting to wonder if it is an opensuse bug. I am thinking about
> switching back to Ubuntu.
>
> On Feb 17, 9:04 pm, Detectedstealth <[email protected]> wrote:
>
>
>
>
>
>
>
> > Yeah I have tried removing settings.pyc and __init__.pyc it
> > regenerates the *.pyc files but still is not reading the database
> > settings for some reason
>
> > On Feb 17, 7:56 am, Furbee <[email protected]> wrote:
>
> > > That is strange. This probably won't help, but try deleting the
> > > settings.pyc file and then run python manage.py runserver again (without
> > > --settings=settings).
>
> > > Furbee
>
> > > On Fri, Feb 17, 2012 at 7:45 AM, Babatunde Akinyanmi
> > > <[email protected]>wrote:
>
> > > > Yes I do get it. I didn't realize that while I was typing my reply
> > > > your message had already been delivered to the group.
>
> > > > On 2/17/12, Detectedstealth <[email protected]> wrote:
> > > > > I can connect with the same credentials that isn't the problem.
>
> > > > > The problem is if I set a password in settings.py it doesn't use a
> > > > > password as the error message states. However when I force the
> > > > > settings file with the --settings option then it reads the file
> > > > > correctly and uses the password.
>
> > > > > On Feb 17, 7:06 am, Babatunde Akinyanmi <[email protected]> wrote:
> > > > >> Try to connect to mysql with the same credentials on your terminal. 
> > > > >> If
> > > > >> it doesn't work then you need to reset your root password.
>
> > > > >> sudo dpkg-reconfigure mysql-server-5.1
>
> > > > >> Should do the trick and then restart the server (That works on 
> > > > >> ubuntu).
>
> > > > >> Also you should consider creating a separate user instead of using 
> > > > >> root.
>
> > > > >> On 2/17/12, Detectedstealth <[email protected]> wrote:
>
> > > > >> > Hi,
>
> > > > >> > I am just coming back to django development after a while of
> > > > >> > developing with pyramid. I have taking over an application.
>
> > > > >> > For some reason with the newest version of django it is not reading
> > > > >> > the password I set in settings:
>
> > > > >> > DATABASES = {
> > > > >> >     'default': {
> > > > >> >         'ENGINE': 'django.db.backends.mysql', # Add
> > > > >> > 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 
> > > > >> > 'oracle'.
> > > > >> >         'NAME': 'mydatabase',                      # Or path to
> > > > >> > database file if using sqlite3.
> > > > >> >         'USER': 'root',                      # Not used with 
> > > > >> > sqlite3.
> > > > >> >         'PASSWORD': 'mypassword',                  # 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.
> > > > >> >     }
> > > > >> > }
>
> > > > >> > When starting the server I get the following error:
> > > > >> > ...MySQL_python-1.2.3-py2.7-linux-x86_64.egg/MySQLdb/connections.py",
> > > > >> > line 187, in
> > > > >> > __init__
> > > > >> > _mysql_exceptions.OperationalError: (1045, "Access denied for user
> > > > >> > 'root'@'localhost' (using password: NO)")
>
> > > > >> > Not sure why it is saying there was not password. For the newest
> > > > >> > version of django is there a new way to tell python manage.py
> > > > >> > runserver what password/username/database to use?
>
> > > > >> > --
> > > > >> > You received this message because you are subscribed to the Google
> > > > >> > Groups
> > > > >> > "Django users" group.
> > > > >> > To post to this group, send email to [email protected].
> > > > >> > To unsubscribe from this group, send email to
> > > > >> > [email protected].
> > > > >> > For more options, visit this group at
> > > > >> >http://groups.google.com/group/django-users?hl=en.
>
> > > > >> --
> > > > >> Sent from my mobile device
>
> > > > > --
> > > > > You received this message because you are subscribed to the Google 
> > > > > Groups
> > > > > "Django users" group.
> > > > > To post to this group, send email to [email protected].
> > > > > To unsubscribe from this group, send email to
> > > > > [email protected].
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/django-users?hl=en.
>
> > > > --
> > > > Sent from my mobile device
>
> > > > --
> > > > You received this message because you are subscribed to the Google 
> > > > Groups
> > > > "Django users" group.
> > > > To post to this group, send email to [email protected].
> > > > To unsubscribe from this group, send email to
> > > > [email protected].
> > > > 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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to