On 12/5/2016 7:44 AM, Derek wrote:
>
> This may be "off topic" - so feel free to disregard! - but why "blogs on
porting from 1.1 to 1.6"? If you are in the process of upgrading, then why
not keep going to at least 1.8, which is the oldest version still receiving
patches and support?
Not off
This may be "off topic" - so feel free to disregard! - but why "blogs on
porting from 1.1 to 1.6"? If you are in the process of upgrading, then why
not keep going to at least 1.8, which is the oldest version still receiving
patches and support?
Some blogs are:
*
...Thanks everyone for the above discussion -- some progress today has been
noted...
To answer Matt's question...
The variable at the root of the error appears to be -- response.
as found in /usr/lib/python2.7/site-packages/django/core/handlers/base.py
line 89
response is assigned as "None"
For what it’s worth, I do get this error sometimes when I am running the
development server, even in Python 3.5 and Django 1.10. But because it’s the
development server, I simply disregard it.
I typically only get this message when I am running several AJAX calls very
close together. (e.g.
Thanks for the reply.
I agree the probability of this being a bug in Django is improbable still I
found git hub django
bug descriptions/discussions which URLs are listed in previous posts. Both
of those URLs
listed patches to fix the situation, not directly in Django but in the
WsgiRef
On Thursday, 1 December 2016 13:16:07 UTC, NoviceSortOf wrote:
>
>
>
> Hi All,
>
> After hours of looking for solutions, here on Stackoverflow, GitHub,
> Django site and other forums,
> and seeing that at least 2 other posts related to what per web chatter
> appears to be a known
> bug in Django
Hi All,
After hours of looking for solutions, here on Stackoverflow, GitHub, Django
site and other forums,
and seeing that at least 2 other posts related to what per web chatter
appears to be a known
bug in Django and the WSGI package, I'm wondering where to turn for useful
advice
regarding
7 matches
Mail list logo
