Re: FieldError, But Only In Production

2014-02-14 Thread Rich Jones
> are you using virtualenv? it's possible that mod_wsgi was executing > in a different environment than the test server. > >Or mod_wsgi is compiled for a different version of python and thus is >finding completely different libraries. Heh, it was neither of those things. No virtualenv on the mac

Re: FieldError, But Only In Production

2014-02-14 Thread Tom Evans
On Fri, Feb 14, 2014 at 12:38 AM, Javier Guerra Giraldez wrote: > On Thu, Feb 13, 2014 at 7:09 PM, Rich Jones wrote: >> We're good now. No idea what the hell was happening, but this works now. >> Humbling to realize how little I know about the ORM internals. > > > are you using virtualenv? it's

Re: FieldError, But Only In Production

2014-02-13 Thread Javier Guerra Giraldez
On Thu, Feb 13, 2014 at 7:09 PM, Rich Jones wrote: > We're good now. No idea what the hell was happening, but this works now. > Humbling to realize how little I know about the ORM internals. are you using virtualenv? it's possible that mod_wsgi was executing in a different environment than the

Re: FieldError, But Only In Production

2014-02-13 Thread Rich Jones
Said fuck it, gave up and used Nginx + Gunicorn. We're good now. No idea what the hell was happening, but this works now. Humbling to realize how little I know about the ORM internals. Thanks for listening, R On Thu, Feb 13, 2014 at 3:13 PM, Rich Jones wrote: > > > Please show how you are doin

Re: FieldError, But Only In Production

2014-02-13 Thread Rich Jones
> Please show how you are doing this. Using mod_wsgi and Apache, using I think a fairly standard .wsgi: import os, sys path = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) if path not in sys.path: sys.path.append(path) sys.path.append('/srv/myapp') os.

Re: FieldError, But Only In Production

2014-02-13 Thread Tom Evans
On Thu, Feb 13, 2014 at 6:00 AM, Rich Jones wrote: > Hey guys! > > I've got a real stumper here. Pulling my hair out over this one, would > really appreciate some options! > > Anywhere in my application that calls user.get_profile() causes a > FieldError.. but only in production. I'm using WSGI an

Re: FieldError, But Only In Production

2014-02-13 Thread Rich Jones
Ah, okay, noted, although I believe this may be a bug in Django itself but want to exhaust everything before I open a ticket. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send

Re: FieldError, But Only In Production

2014-02-13 Thread Javier Guerra Giraldez
On Thu, Feb 13, 2014 at 5:49 PM, Rich Jones wrote: > Since this seems to happening at a pretty deep level, would it be uncouth to > kick this over do django-dev? django-dev is not 'django support, level 2'. it's about the development of the Django framework. if you have a concrete proposal, or

Re: FieldError, But Only In Production

2014-02-13 Thread Rich Jones
Since this seems to happening at a pretty deep level, would it be uncouth to kick this over do django-dev? On Thu, Feb 13, 2014 at 9:17 AM, Rich Jones wrote: > Yes, all of these things worked just fine. The code is in the _same > location_ on the _same machine_ with the _same settings_ and the

Re: FieldError, But Only In Production

2014-02-13 Thread Rich Jones
Yes, all of these things worked just fine. The code is in the _same location_ on the _same machine_ with the _same settings_ and the _same database_. The only difference is devserver vs Apache. :( On Thu, Feb 13, 2014 at 2:21 AM, Vibhu Rishi wrote: > Seems to me somewhere in the code it is try

Re: FieldError, But Only In Production

2014-02-13 Thread Vibhu Rishi
Seems to me somewhere in the code it is trying to put user into a field instead of treating it as a table. Basic sanity checks : - is the djagno versions on both production and local same ? - same for wsgi and apache ? - syncdb worked fine ? V. On Thu, Feb 13, 2014 at 11:30 AM, Rich Jones wrot