[google-appengine] Re: Model Inheritance caveat

[allyourcode]

There is PolyModel, which will return subclass instances when queried. Not 
sure if that existed at the time, but it sounds like exactly what you are 
looking for. e.g.

from google.appengine.db import polymodel  # ndb also has this

class P(polymodel.PolyModel): pass
class C1(P): pass
class C2(P): pass

P.all()  # May return instances of C1 and/or C2.


On Friday, August 1, 2008 7:30:28 AM UTC-7, Rein Petersen wrote:

 Andreas, thanks for that :) 
 I'll be relating the entities using parent-child relationships. It is 
 unfortunate that you cannot query a base model and find the subclasses 
 - oh well, don't want to throw the baby out with the bathwater... 
 Thanks again, 
 Rein 

 On Aug 1, 9:09 am, Blixt andreasbl...@gmail.com wrote: 
  You use the 'pass' keyword in Python to skip an implementation: 
  class Region(Place): 
pass 
  
  Also worth noting is that data-wise, those models will have no 
  relation to eachother in the datastore, so you can only query for one 
  type at a time. Just in case you didn't consider it, might save you 
  some time :) 
  
  Regards, 
  Andreas 
  
  On Aug 1, 4:05 pm, Rein Petersen rein.peter...@gmail.com wrote: 
  
   Hi All, 
  
   I'm using Model inheritance to distinguish distinguish entities that 
   are, essentially, the same. Usually, inheritance involves extending 
   the base class with more properties (and such) defined in the 
   subclasses but in my instance, extension is not required - only 
   distinction. An example is provided below. 
  
   The problem is that an exception is raised when there is no code below 
   the class definition: 
  
   type 'exceptions.IndentationError': expected an indented block 
  
   I could easily give up using inheritance and define the properties on 
   each model separately, or I could continue with inheritance but pull 
   one property out of the base and repeat it in the subclasses but it 
   pains me to do so. 
  
   I was wondering if there were some little bit of insignificant I place 
   in the subclass definitions that would satisfy the interpreter to 
   avoid the IndentationError exception... Thanks Rein :) 
  
   *** Example :: models.py 
   class Place(db.Model): 
 # abstract 
 name = db.StringProperty() 
 geo = db.GeoPtProperty() 
  
   class Continent(Place): 
 # represents a continent 
  
   class Continent(Place): 
 # represents a continent 
  
   class Country(Place): 
 # represents a country 
  
   class Region(Place): 
 # represents a region 
  
   class City(Place): 
 # reprecents a city

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Model Inheritance caveat

[allyourcode]

On Saturday, August 2, 2008 11:26:12 AM UTC-7, Rein Petersen wrote:

 Thanks for the advice but I remain skeptical - I prefer that the 
 entities are stored in separate groups for speed's sake. If I want to 
 fetch Continents (there are only 7), I don't want to search an entity 
 group that includes 100's of 1000's of cities, regions, and 
 countries...


Datastore queries are designed to scale with the number of results, not the 
number entities. It shouldn't matter that your 100s of countries are mixed 
with 1s of cities. If you find that it does, report it.

Having said that, putting continents into Datastore may be going for too 
much purity and/or elegance. Geological shifts happen slowly enough that 
your app (and the rest of civilization?) probably won't be around by the 
time South America and Africa reunite, or California sucedes from North 
America.
 

 Also, I do expect to uniquely extend the subclasses with 
 properties - I just don't know what they are yet... I'm still 
 designing. 

 Calvin, I'm curious why this is frowned upon in Python. Can you tell 
 me why or where I can read more about it? I'm so accustomed 
 abstracting and normalizing all the way as good OO and db design, 
 but if this can be problematic in some instances with Python and/or 
 with the GAE datastore, I want to know - my purpose is to design for 
 performance and scalability on this platform and I am all ears on the 
 matter.


Your idea to model with subclasses sounds good to me. This seems to be 
something that PolyModel was designed for.
 


 Thanks again for all the advice :) 
 Rein 

 On Aug 1, 3:43 pm, Blixt andreasbl...@gmail.com wrote: 
  I agree. Something like: 
  class Area(db.Model): 
CONTINENT = 1 
COUNTRY = 2 
REGION = 3 
CITY = 4 
  
name = db.StringProperty() 
geo = db.GeoPtProperty() 
level = db.IntegerProperty(choices = [Area.CONTINENT, Area.COUNTRY, 
  Area.REGION, Area.CITY]) 
  
  On Aug 1, 7:25 pm, Calvin Spealman ironfro...@gmail.com wrote: 
  
   Usually this kind of dependence on type is frowned upon in Python. If 
   the only difference between classes is the name, and otherwise they 
   are completely identical: the name should be the same too. I've never 
   seen a good reason to do this, and I've seen dozens of people with 
   cases where they thought it was a good idea. Another design has always 
   prevailed. 
  
   Are these all not simply places? Why not add a CategoryProperty? 
  
   On Fri, Aug 1, 2008 at 10:05 AM, Rein Petersen 
 rein.peter...@gmail.com wrote: 
  
Hi All, 
  
I'm using Model inheritance to distinguish distinguish entities that 
are, essentially, the same. Usually, inheritance involves extending 
the base class with more properties (and such) defined in the 
subclasses but in my instance, extension is not required - only 
distinction. An example is provided below. 
  
The problem is that an exception is raised when there is no code 
 below 
the class definition: 
  
type 'exceptions.IndentationError': expected an indented block 
  
I could easily give up using inheritance and define the properties 
 on 
each model separately, or I could continue with inheritance but pull 
one property out of the base and repeat it in the subclasses but it 
pains me to do so. 
  
I was wondering if there were some little bit of insignificant I 
 place 
in the subclass definitions that would satisfy the interpreter to 
avoid the IndentationError exception... Thanks Rein :) 
  
*** Example :: models.py 
class Place(db.Model): 
 # abstract 
 name = db.StringProperty() 
 geo = db.GeoPtProperty() 
  
class Continent(Place): 
 # represents a continent 
  
class Continent(Place): 
 # represents a continent 
  
class Country(Place): 
 # represents a country 
  
class Region(Place): 
 # represents a region 
  
class City(Place): 
 # reprecents a city 
  
   -- 
   Read my blog! I depend on your acceptance of my opinion! I am 
 interesting!http://ironfroggy-code.blogspot.com/

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] logging format string

[allyourcode]

Is there a way to change the format string that app engine uses? I've
tried adding the following line to my handler script's main function:

logging.basicConfig(format=foo)

Unfortunately, that doesn't change what I see in my development
server's window. I'm not really familiar with the logging module, but
from what I've gather from the (voluminous!!) documentation, this
seems to be the right way to do things, at least out side of GAE.
What's the right way to do this in GAE? Is it even possible?

Here's the info on my dev env:

Windows XP Home SP3
SDK 1.3.5
google-app-engine-django r105
Django 1.0

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: TemplateDoesNotExist: css/datastore.css

[allyourcode]

 of the problem is if you go to
  http://localhost:8000/_ah/admin/interactive
   and enter a correct program, and it hit Run Program, the following
   output is (sporadically) generated:

   Traceback (most recent call last):
    File c:\Program Files\Google\google_appengine\google\appengine\ext
   \webapp\__init__.py, line 507, in __call__
      handler.get(*groups)
    File C:\Program Files\Google\google_appengine\google\appengine\ext
   \admin\__init__.py, line 737, in get
      self.generate('datastore.html', values)
    File C:\Program Files\Google\google_appengine\google\appengine\ext
   \admin\__init__.py, line 131, in generate
      self.response.out.write(template.render(path, values,
   debug=_DEBUG))
    File c:\Program Files\Google\google_appengine\google\appengine\ext
   \webapp\template.py, line 80, in render
      t = load(template_path, debug)
    File c:\Program Files\Google\google_appengine\google\appengine\ext
   \webapp\template.py, line 108, in load
      template = django.template.loader.get_template(file_name)
    File app_root\django.zip\django\template\loader.py, line 81, in
   get_template
    File app_root\django.zip\django\template\loader.py, line 89, in
   get_template_from_string
    File app_root\django.zip\django\template\__init__.py, line 166,
   in __init__
    File app_root\django.zip\django\template\__init__.py, line 187,
   in compile_string
    File app_root\django.zip\django\template\__init__.py, line 283,
   in parse
    File app_root\django.zip\django\template\loader_tags.py, line
   169, in do_extends
    File app_root\django.zip\django\template\__init__.py, line 283,
   in parse
    File app_root\django.zip\django\template\loader_tags.py, line
   147, in do_block
    File app_root\django.zip\django\template\__init__.py, line 283,
   in parse
    File app_root\django.zip\django\template\loader_tags.py, line
   187, in do_include
    File app_root\django.zip\django\template\loader_tags.py, line
   102, in __init__
    File app_root\django.zip\django\template\loader.py, line 80, in
   get_template
    File app_root\django.zip\django\template\loader.py, line 73, in
   find_template_source
   TemplateDoesNotExist: css/datastore.css

   When I restart the server, visit some pages in my app in another
   window, and go back to the original window containing the script was
   trying to run in the Interactive Console, I'm able to run it
   successfully without modification (this is how I know the program is
   correct).

   Here are my versions:

   GAE SDK 1.2.7
   Django 1.0
   GAE Django Helper r95
   Python 2.5.4
   Windows XP Home Edition SP3

   I know there's a new version of the SDK, but when I tried upgrading,
   my app stopped working, so I reinstalled version 1.2.7, which is
   (otherwise) working fine for me.

   I know other people have experienced this. Has anyone found a
   solution?

   Thanks,

  allyourcode

   --
   You received this message because you are subscribed to the Google 
   Groups
   Google App Engine group.
   To post to this group, send email to google-appeng...@googlegroups.com.
   To unsubscribe from this group, send email to
   google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib
e...@googlegroups.com
   .
   For more options, visit this group at
  http://groups.google.com/group/google-appengine?hl=en.

   --
   Nick Johnson, Developer Programs Engineer, App Engine Google Ireland 
   Ltd. ::
   Registered in Dublin, Ireland, Registration Number: 368047
   Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration 
   Number:
   368047

   --
   You received this message because you are subscribed to the Google 
   Groups Google App Engine group.
   To post to this group, send email to google-appeng...@googlegroups.com.
   To unsubscribe from this group, send email to 
   google-appengine+unsubscr...@googlegroups.com.
   For more options, visit this group 
   athttp://groups.google.com/group/google-appengine?hl=en.

   --
   You received this message because you are subscribed to the Google Groups 
   Google App Engine group.
   To post to this group, send email to google-appeng...@googlegroups.com.
   To unsubscribe from this group, send email to 
   google-appengine+unsubscr...@googlegroups.com.
   For more options, visit this group 
   athttp://groups.google.com/group/google-appengine?hl=en.

  --
  Fredrik Bonander
  carl.fredrik.bonan...@gmail.com
  +46 70 943 5441

  - the infinite power of the creative mind -

  --
  You received this message because you are subscribed to the Google Groups 
  Google App Engine group.
  To post to this group, send email to google-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://groups.google.com/group/google-appengine?hl=en.

 --
 You received this message because you are subscribed to the Google Groups 
 Google App Engine group.
 To post

[google-appengine] Re: TemplateDoesNotExist: css/datastore.css

[allyourcode]

So, I finally tried installing version 1.3.4 of the SDK, which was a
bit of a headache, because my dev site would not start up after I did
this. I think this is due to 
https://code.google.com/p/google-app-engine-django/issues/detail?id=161
. To work around the issue, I added ipaddr supplied with the SDK to my
PYTHONPATH. I'm able to start my site now, but my original issue
(TemplateDoesNotExist) hasn't stopped happening. Another symptom of
the problem is different uncaught TemplateDoesNotExist exception with
the following message:

Your TEMPLATE_DIRS setting is empty. Change it to point to at least
one template directory.

This doesn't make sense, because my settings.py includes the
following:

TEMPLATE_DIRS = (
os.path.join(ROOT_PATH, 'templates')
)

This is why I believe TEMPLATE_DIRS is being cleared at some point,
something that I would never do in my app code. Another observation
that supports this theory is that the problem generally goes away when
I restart my server (I might have mentioned this before).

I'm going to try working around this by using the svn version of
google-app-engine-django (r105), but I haven't been able to use it it
for long, so I'm not sure if it'll make the problem go away.

grr...

On May 8, 5:27 am, allyourcode allyourc...@gmail.com wrote:
 I think the problem is that my TEMPLATE_DIRS gets cleared at some
 point, even though my app doesn't do that, at least not directly. My
 guess is that this is happening somewhere in the SDK or Django helper
 to implement the admin pages, but I can't tell which piece is doing
 the manipulation :/.

 I'll try to upgrade my SDK, but again, when I tried this before, my
 app ended up dead in the water (forget what issues I was running into
 before).

 On May 7, 2:08 am, Nick Johnson (Google) nick.john...@google.com
 wrote:



  Hi,

  It's impossible to suggest what might be wrong without seeing the code in
  question. It looks like you're probably running into problems with relative
  or absolute paths, or your css file is marked as static in your app.yaml.

  You should definitely upgrade your SDK - 1.3.3 is the latest version, and
  1.2.7 is very much out of date.

  -Nick Johnson

  On Fri, May 7, 2010 at 1:00 AM,allyourcodeallyourc...@gmail.com wrote:
   Hi,

   I'm having a problem developing my GAE application. It's been reported
   as issue 464 on the GAE issue tracker, but it's not getting any
   attention, due to difficulties with reproducing the issue; hence, I'm
   turning to the GAE group to look for support.

   Restarting the dev server temporarily gets rid of the problem, but it
   keeps coming back. I'm worried this problem will come up in
   production, but we haven't released our app yet, so I've never had a
   chance to see how it works in production.

   One symptom of the problem is if you go to
  http://localhost:8000/_ah/admin/interactive
   and enter a correct program, and it hit Run Program, the following
   output is (sporadically) generated:

   Traceback (most recent call last):
    File c:\Program Files\Google\google_appengine\google\appengine\ext
   \webapp\__init__.py, line 507, in __call__
      handler.get(*groups)
    File C:\Program Files\Google\google_appengine\google\appengine\ext
   \admin\__init__.py, line 737, in get
      self.generate('datastore.html', values)
    File C:\Program Files\Google\google_appengine\google\appengine\ext
   \admin\__init__.py, line 131, in generate
      self.response.out.write(template.render(path, values,
   debug=_DEBUG))
    File c:\Program Files\Google\google_appengine\google\appengine\ext
   \webapp\template.py, line 80, in render
      t = load(template_path, debug)
    File c:\Program Files\Google\google_appengine\google\appengine\ext
   \webapp\template.py, line 108, in load
      template = django.template.loader.get_template(file_name)
    File app_root\django.zip\django\template\loader.py, line 81, in
   get_template
    File app_root\django.zip\django\template\loader.py, line 89, in
   get_template_from_string
    File app_root\django.zip\django\template\__init__.py, line 166,
   in __init__
    File app_root\django.zip\django\template\__init__.py, line 187,
   in compile_string
    File app_root\django.zip\django\template\__init__.py, line 283,
   in parse
    File app_root\django.zip\django\template\loader_tags.py, line
   169, in do_extends
    File app_root\django.zip\django\template\__init__.py, line 283,
   in parse
    File app_root\django.zip\django\template\loader_tags.py, line
   147, in do_block
    File app_root\django.zip\django\template\__init__.py, line 283,
   in parse
    File app_root\django.zip\django\template\loader_tags.py, line
   187, in do_include
    File app_root\django.zip\django\template\loader_tags.py, line
   102, in __init__
    File app_root\django.zip\django\template\loader.py, line 80, in
   get_template
    File app_root\django.zip\django\template\loader.py, line 73, in
   find_template_source
   TemplateDoesNotExist: css

[google-appengine] Re: TemplateDoesNotExist: css/datastore.css

[allyourcode]

After upgrading my sdk (to 1.3.4) and google-app-engine-django (to
r105), I'm still having problems with sporadic TemplateDoesNotExist
errors.

On Jun 18, 3:03 pm, allyourcode allyourc...@gmail.com wrote:
 So, I finally tried installing version 1.3.4 of the SDK, which was a
 bit of a headache, because my dev site would not start up after I did
 this. I think this is due 
 tohttps://code.google.com/p/google-app-engine-django/issues/detail?id=161
 . To work around the issue, I added ipaddr supplied with the SDK to my
 PYTHONPATH. I'm able to start my site now, but my original issue
 (TemplateDoesNotExist) hasn't stopped happening. Another symptom of
 the problem is different uncaught TemplateDoesNotExist exception with
 the following message:

 Your TEMPLATE_DIRS setting is empty. Change it to point to at least
 one template directory.

 This doesn't make sense, because my settings.py includes the
 following:

 TEMPLATE_DIRS = (
     os.path.join(ROOT_PATH, 'templates')
 )

 This is why I believe TEMPLATE_DIRS is being cleared at some point,
 something that I would never do in my app code. Another observation
 that supports this theory is that the problem generally goes away when
 I restart my server (I might have mentioned this before).

 I'm going to try working around this by using the svn version of
 google-app-engine-django (r105), but I haven't been able to use it it
 for long, so I'm not sure if it'll make the problem go away.

 grr...

 On May 8, 5:27 am,allyourcodeallyourc...@gmail.com wrote:

  I think the problem is that my TEMPLATE_DIRS gets cleared at some
  point, even though my app doesn't do that, at least not directly. My
  guess is that this is happening somewhere in the SDK or Django helper
  to implement the admin pages, but I can't tell which piece is doing
  the manipulation :/.

  I'll try to upgrade my SDK, but again, when I tried this before, my
  app ended up dead in the water (forget what issues I was running into
  before).

  On May 7, 2:08 am, Nick Johnson (Google) nick.john...@google.com
  wrote:

   Hi,

   It's impossible to suggest what might be wrong without seeing the code in
   question. It looks like you're probably running into problems with 
   relative
   or absolute paths, or your css file is marked as static in your app.yaml.

   You should definitely upgrade your SDK - 1.3.3 is the latest version, and
   1.2.7 is very much out of date.

   -Nick Johnson

   On Fri, May 7, 2010 at 1:00 AM,allyourcodeallyourc...@gmail.com wrote:
Hi,

I'm having a problem developing my GAE application. It's been reported
as issue 464 on the GAE issue tracker, but it's not getting any
attention, due to difficulties with reproducing the issue; hence, I'm
turning to the GAE group to look for support.

Restarting the dev server temporarily gets rid of the problem, but it
keeps coming back. I'm worried this problem will come up in
production, but we haven't released our app yet, so I've never had a
chance to see how it works in production.

One symptom of the problem is if you go to
   http://localhost:8000/_ah/admin/interactive
and enter a correct program, and it hit Run Program, the following
output is (sporadically) generated:

Traceback (most recent call last):
 File c:\Program Files\Google\google_appengine\google\appengine\ext
\webapp\__init__.py, line 507, in __call__
   handler.get(*groups)
 File C:\Program Files\Google\google_appengine\google\appengine\ext
\admin\__init__.py, line 737, in get
   self.generate('datastore.html', values)
 File C:\Program Files\Google\google_appengine\google\appengine\ext
\admin\__init__.py, line 131, in generate
   self.response.out.write(template.render(path, values,
debug=_DEBUG))
 File c:\Program Files\Google\google_appengine\google\appengine\ext
\webapp\template.py, line 80, in render
   t = load(template_path, debug)
 File c:\Program Files\Google\google_appengine\google\appengine\ext
\webapp\template.py, line 108, in load
   template = django.template.loader.get_template(file_name)
 File app_root\django.zip\django\template\loader.py, line 81, in
get_template
 File app_root\django.zip\django\template\loader.py, line 89, in
get_template_from_string
 File app_root\django.zip\django\template\__init__.py, line 166,
in __init__
 File app_root\django.zip\django\template\__init__.py, line 187,
in compile_string
 File app_root\django.zip\django\template\__init__.py, line 283,
in parse
 File app_root\django.zip\django\template\loader_tags.py, line
169, in do_extends
 File app_root\django.zip\django\template\__init__.py, line 283,
in parse
 File app_root\django.zip\django\template\loader_tags.py, line
147, in do_block
 File app_root\django.zip\django\template\__init__.py, line 283,
in parse
 File app_root\django.zip\django\template\loader_tags.py, line
187

[google-appengine] Re: TemplateDoesNotExist: css/datastore.css

[allyourcode]

I think the problem is that my TEMPLATE_DIRS gets cleared at some
point, even though my app doesn't do that, at least not directly. My
guess is that this is happening somewhere in the SDK or Django helper
to implement the admin pages, but I can't tell which piece is doing
the manipulation :/.

I'll try to upgrade my SDK, but again, when I tried this before, my
app ended up dead in the water (forget what issues I was running into
before).

On May 7, 2:08 am, Nick Johnson (Google) nick.john...@google.com
wrote:
 Hi,

 It's impossible to suggest what might be wrong without seeing the code in
 question. It looks like you're probably running into problems with relative
 or absolute paths, or your css file is marked as static in your app.yaml.

 You should definitely upgrade your SDK - 1.3.3 is the latest version, and
 1.2.7 is very much out of date.

 -Nick Johnson



 On Fri, May 7, 2010 at 1:00 AM, allyourcode allyourc...@gmail.com wrote:
  Hi,

  I'm having a problem developing my GAE application. It's been reported
  as issue 464 on the GAE issue tracker, but it's not getting any
  attention, due to difficulties with reproducing the issue; hence, I'm
  turning to the GAE group to look for support.

  Restarting the dev server temporarily gets rid of the problem, but it
  keeps coming back. I'm worried this problem will come up in
  production, but we haven't released our app yet, so I've never had a
  chance to see how it works in production.

  One symptom of the problem is if you go to
 http://localhost:8000/_ah/admin/interactive
  and enter a correct program, and it hit Run Program, the following
  output is (sporadically) generated:

  Traceback (most recent call last):
   File c:\Program Files\Google\google_appengine\google\appengine\ext
  \webapp\__init__.py, line 507, in __call__
     handler.get(*groups)
   File C:\Program Files\Google\google_appengine\google\appengine\ext
  \admin\__init__.py, line 737, in get
     self.generate('datastore.html', values)
   File C:\Program Files\Google\google_appengine\google\appengine\ext
  \admin\__init__.py, line 131, in generate
     self.response.out.write(template.render(path, values,
  debug=_DEBUG))
   File c:\Program Files\Google\google_appengine\google\appengine\ext
  \webapp\template.py, line 80, in render
     t = load(template_path, debug)
   File c:\Program Files\Google\google_appengine\google\appengine\ext
  \webapp\template.py, line 108, in load
     template = django.template.loader.get_template(file_name)
   File app_root\django.zip\django\template\loader.py, line 81, in
  get_template
   File app_root\django.zip\django\template\loader.py, line 89, in
  get_template_from_string
   File app_root\django.zip\django\template\__init__.py, line 166,
  in __init__
   File app_root\django.zip\django\template\__init__.py, line 187,
  in compile_string
   File app_root\django.zip\django\template\__init__.py, line 283,
  in parse
   File app_root\django.zip\django\template\loader_tags.py, line
  169, in do_extends
   File app_root\django.zip\django\template\__init__.py, line 283,
  in parse
   File app_root\django.zip\django\template\loader_tags.py, line
  147, in do_block
   File app_root\django.zip\django\template\__init__.py, line 283,
  in parse
   File app_root\django.zip\django\template\loader_tags.py, line
  187, in do_include
   File app_root\django.zip\django\template\loader_tags.py, line
  102, in __init__
   File app_root\django.zip\django\template\loader.py, line 80, in
  get_template
   File app_root\django.zip\django\template\loader.py, line 73, in
  find_template_source
  TemplateDoesNotExist: css/datastore.css

  When I restart the server, visit some pages in my app in another
  window, and go back to the original window containing the script was
  trying to run in the Interactive Console, I'm able to run it
  successfully without modification (this is how I know the program is
  correct).

  Here are my versions:

  GAE SDK 1.2.7
  Django 1.0
  GAE Django Helper r95
  Python 2.5.4
  Windows XP Home Edition SP3

  I know there's a new version of the SDK, but when I tried upgrading,
  my app stopped working, so I reinstalled version 1.2.7, which is
  (otherwise) working fine for me.

  I know other people have experienced this. Has anyone found a
  solution?

  Thanks,

  allyourcode

  --
  You received this message because you are subscribed to the Google Groups
  Google App Engine group.
  To post to this group, send email to google-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.

 --
 Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. ::
 Registered in Dublin, Ireland, Registration Number: 368047
 Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
 368047

 --
 You received

[google-appengine] TemplateDoesNotExist: css/datastore.css

[allyourcode]

Hi,

I'm having a problem developing my GAE application. It's been reported
as issue 464 on the GAE issue tracker, but it's not getting any
attention, due to difficulties with reproducing the issue; hence, I'm
turning to the GAE group to look for support.

Restarting the dev server temporarily gets rid of the problem, but it
keeps coming back. I'm worried this problem will come up in
production, but we haven't released our app yet, so I've never had a
chance to see how it works in production.

One symptom of the problem is if you go to 
http://localhost:8000/_ah/admin/interactive
and enter a correct program, and it hit Run Program, the following
output is (sporadically) generated:

Traceback (most recent call last):
  File c:\Program Files\Google\google_appengine\google\appengine\ext
\webapp\__init__.py, line 507, in __call__
handler.get(*groups)
  File C:\Program Files\Google\google_appengine\google\appengine\ext
\admin\__init__.py, line 737, in get
self.generate('datastore.html', values)
  File C:\Program Files\Google\google_appengine\google\appengine\ext
\admin\__init__.py, line 131, in generate
self.response.out.write(template.render(path, values,
debug=_DEBUG))
  File c:\Program Files\Google\google_appengine\google\appengine\ext
\webapp\template.py, line 80, in render
t = load(template_path, debug)
  File c:\Program Files\Google\google_appengine\google\appengine\ext
\webapp\template.py, line 108, in load
template = django.template.loader.get_template(file_name)
  File app_root\django.zip\django\template\loader.py, line 81, in
get_template
  File app_root\django.zip\django\template\loader.py, line 89, in
get_template_from_string
  File app_root\django.zip\django\template\__init__.py, line 166,
in __init__
  File app_root\django.zip\django\template\__init__.py, line 187,
in compile_string
  File app_root\django.zip\django\template\__init__.py, line 283,
in parse
  File app_root\django.zip\django\template\loader_tags.py, line
169, in do_extends
  File app_root\django.zip\django\template\__init__.py, line 283,
in parse
  File app_root\django.zip\django\template\loader_tags.py, line
147, in do_block
  File app_root\django.zip\django\template\__init__.py, line 283,
in parse
  File app_root\django.zip\django\template\loader_tags.py, line
187, in do_include
  File app_root\django.zip\django\template\loader_tags.py, line
102, in __init__
  File app_root\django.zip\django\template\loader.py, line 80, in
get_template
  File app_root\django.zip\django\template\loader.py, line 73, in
find_template_source
TemplateDoesNotExist: css/datastore.css

When I restart the server, visit some pages in my app in another
window, and go back to the original window containing the script was
trying to run in the Interactive Console, I'm able to run it
successfully without modification (this is how I know the program is
correct).

Here are my versions:

GAE SDK 1.2.7
Django 1.0
GAE Django Helper r95
Python 2.5.4
Windows XP Home Edition SP3

I know there's a new version of the SDK, but when I tried upgrading,
my app stopped working, so I reinstalled version 1.2.7, which is
(otherwise) working fine for me.

I know other people have experienced this. Has anyone found a
solution?

Thanks,

allyourcode

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.