Re: empty request object

2016-02-29 Thread Larry Martell
Yes, I'm an idiot. I had commented out the middleware when debugging and forgot to put them back. On Mon, Feb 29, 2016 at 10:09 AM, knbk wrote: > That would happen if the AuthenticationMiddleware hasn't run. In what > context is request.user missing? > > On Monday, February 29, 2016 at 3:54:24 PM

Re: empty request object

2016-02-29 Thread knbk
That would happen if the AuthenticationMiddleware hasn't run. In what context is request.user missing? On Monday, February 29, 2016 at 3:54:24 PM UTC+1, larry@gmail.com wrote: > > So does anyone know why there would be a no user attr? I would expect > this: > > (Pdb) request.user > > > B

Re: empty request object

2016-02-29 Thread Larry Martell
So does anyone know why there would be a no user attr? I would expect this: (Pdb) request.user But I get this: (Pdb) request.user *** AttributeError: 'WSGIRequest' object has no attribute 'user' On Sat, Feb 27, 2016 at 6:31 PM, Larry Martell wrote: > Yes, you are absolutely correct. Thanks fo

Re: empty request object

2016-02-27 Thread Larry Martell
Yes, you are absolutely correct. Thanks for directing me away from that red herring. But it seems request.user no longer exists. There is code that does this: if request.user.is_authenticated(): which throws: AttributeError: "'WSGIRequest' object has no attribute 'user'" On Sat, Feb 27, 2016 a

Re: empty request object

2016-02-27 Thread knbk
I was referring to the wrong release notes. The rights one can be found in the 1.8 release notes in the miscellaneous section[1]: HttpRequest > > now > has a simplified repr (e.g. ). This won’t > change the

Re: empty request object

2016-02-27 Thread Larry Martell
On Sat, Feb 27, 2016 at 5:14 PM, knbk wrote: > The `__repr__` method on HttpRequest was simplified in 1.9[1]. It is not an > accurate description of what is actually contained in the request, and I > doubt it has anything to do with the actual issues you're facing. > > [1] > https://docs.djangopro

Re: empty request object

2016-02-27 Thread knbk
The `__repr__` method on HttpRequest was simplified in 1.9[1]. It is not an accurate description of what is actually contained in the request, and I doubt it has anything to do with the actual issues you're facing. [1] https://docs.djangoproject.com/en/1.9/releases/1.9/#httprequest-details-in-

Re: empty request object

2016-02-27 Thread Larry Martell
On Sat, Feb 27, 2016 at 5:02 PM, James Schneider wrote: > > On Feb 27, 2016 1:55 PM, "Larry Martell" wrote: >> >> Anyone have any insights on this? Is there anything special I need to >> do get the request structure? The way this 1.9 site is now, it doesn't >> work at all because the request stru

Re: empty request object

2016-02-27 Thread James Schneider
On Feb 27, 2016 1:55 PM, "Larry Martell" wrote: > > Anyone have any insights on this? Is there anything special I need to > do get the request structure? The way this 1.9 site is now, it doesn't > work at all because the request structure is not getting passed in. > I'd be most suspicious of midd

Re: empty request object

2016-02-27 Thread Larry Martell
Anyone have any insights on this? Is there anything special I need to do get the request structure? The way this 1.9 site is now, it doesn't work at all because the request structure is not getting passed in. On Fri, Feb 26, 2016 at 10:09 PM, Larry Martell wrote: > I just integrated a broken djan

empty request object

2016-02-26 Thread Larry Martell
I just integrated a broken django setup, 1.9, python 2.7, nginx, uWSGI, RHEL 6. First thing I observed, the views are not receiving anything in the request object, e.g.: (Pdb) print request Other django systems I've worked with I always get something, e.g.: (Pdb) print request , POST:, COOKIES: