Yes indeed! That was it. I am following a tutorial for getting things
running on a Heroku platform and that seems to be something special for
that environment. Thank you!!
On Thursday, December 27, 2012 12:52:57 PM UTC-5, donarb wrote:
>
> On Thursday, December 27, 2012 8:51:11 AM UTC-8, Dan
On Thursday, December 27, 2012 8:51:11 AM UTC-8, Dan Richards wrote:
>
> Yeah, psycopg2 is definitely installed...
>
I noticed that you are using djcelery (which I know nothing about), but
have you tried getting everything working without it first? There's a line
in your settings that says
DATA
On Thursday, December 27, 2012 8:51:11 AM UTC-8, Dan Richards wrote:
>
> Yeah, psycopg2 is definitely installed...
>
> On Thursday, December 27, 2012 9:03:31 AM UTC-5, ke1g wrote:
>>
>>
>>
>> On Thu, Dec 27, 2012 at 8:26 AM, Dan Richards wrote:
>>
>>> Hmmm...well that isn't working either - same
On Thu, Dec 27, 2012 at 11:51 AM, Dan Richards wrote:
> Yeah, psycopg2 is definitely installed...
>
It sounds like it may be time to insert:
import pdb;pdb.set_trace()
at the point where the exception gets raised. Looking at variables that it
doesn't like, and looking up the stack frame f
Yeah, psycopg2 is definitely installed...
On Thursday, December 27, 2012 9:03:31 AM UTC-5, ke1g wrote:
>
>
>
> On Thu, Dec 27, 2012 at 8:26 AM, Dan Richards
> > wrote:
>
>> Hmmm...well that isn't working either - same error. My method for
>> verifying it's picking up the right settings.py is by
On Thu, Dec 27, 2012 at 8:26 AM, Dan Richards wrote:
> Hmmm...well that isn't working either - same error. My method for
> verifying it's picking up the right settings.py is by putting a syntax
> error in the settings.py it should be using and seeing that it generates an
> error. This is the se
Hmmm...well that isn't working either - same error. My method for
verifying it's picking up the right settings.py is by putting a syntax
error in the settings.py it should be using and seeing that it generates an
error. This is the settings.py file in the directory below my app
directory and
Ok. I would try setting the ENGINE value to *sqlite3* and try running *syncdb
*again. If that works (which it should), then we can presume it's a
configuration access problem with the DB.
On 26 December 2012 13:18, Dan Richards wrote:
> NO, just me messing around that it made no difference. I
NO, just me messing around that it made no difference. I have the db
access to all and trust and the error doesn't change no matter what I use
there. It feels like it could be a permissions problem, but I don't know
how to track it down other than to verify I can access postgres via psql
whic
Are the user and password fields meant to be blank?
Cheers,
Ryan
On Dec 26, 2012, at 9:40 AM, Dan Richards wrote:
> First off, I am a newbie to django, python and postgres - so I suspect I am
> missing something obvious, but I am stumped. Any ideas will be gratefully
> accepted...
>
> I ge
First off, I am a newbie to django, python and postgres - so I suspect I am
missing something obvious, but I am stumped. Any ideas will be gratefully
accepted...
I get the popular "Improperly configured settings.DATABASES" error message
when I run syncdb on my test app. I am running:
django
11 matches
Mail list logo
