search

straight55b / app-engine-patch

Automatically exported from code.google.com/p/app-engine-patch
0 stars 0 forks source link

'module' object has no attribute 'ROOT_URLCONF' #172

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Occasionally I've been getting a "'module' object has no attribute 
'ROOT_URLCONF'" error. The attached patch implements the fix recommended by 
<http://code.google.com/appengine/kb/commontasks.html#root_urlconf>.

Original issue reported on code.google.com by dvd...@gmail.com on 24 Jun 2009 at 10:12

Attachments:

GoogleCodeExporter commented 9 years ago 
Which version of app-engine-patch did you use that cause this error?

If it was the repo version, did the error also happen with the latest repo 
version?

Does this happen on production or only on localhost? I know that this bug can 
happen 
on localhost if you first visit the _ah/admin URL and then try to use Django.

That bug could have been caused by something else which was fixed in the latest 
release. The way you fix it now will consume too much CPU. Also, the 
recommended fix 
is for the integrated Django version, only, but we don't use that Django 
version, so 
it would be strange if that bug applied to us.

Original comment by wkornew...@gmail.com on 24 Jun 2009 at 3:45

GoogleCodeExporter commented 9 years ago 
You're right, it does seem to mostly happen after visiting _ah/admin first. 
However, 
I'm fairly sure the error has also occurred when _ah/admin wasn't the *first* 
URL I 
visited, but it was immediately after visiting _ah/admin. This second situation 
only 
seems to occur after the server has been running for >30min (and doesn't always 
happen), so it's difficult to reproduce. I'm using 1.0.2.1, and have only been 
able 
to reproduce the first situation with the latest repo version.

I've only been getting this error on localhost - I haven't uploaded the app to 
production yet.

Original comment by dvd...@gmail.com on 25 Jun 2009 at 1:29

GoogleCodeExporter commented 9 years ago 
I'll have look later. Maybe there is a way to detect this bug...

Original comment by wkornew...@gmail.com on 26 Jun 2009 at 12:50

GoogleCodeExporter commented 9 years ago 
OK, it looks like this bug can't be fixed at the app-engine-patch level. After 
setting 
settings._target=None you can't go back to the datastore admin. The problem is 
that 
both the datastore admin and app-engine-patch require different settings, but 
they use 
the same settings module. Please report to Google that their admin interface 
patches 
Django in a way that influences other app.yaml handlers and they'll have to 
find a 
different solution (e.g., reset their stuff after every request or use absolute 
paths 
when rendering templates).

Original comment by wkornew...@gmail.com on 28 Jun 2009 at 1:44