Appengine has got two modes of operation.
High traffic applications are served directly out of the cache within
a second for example.
For low traffic applications first the uploded code has to be prepared
(unzipped for example) and put into the cache before it can be served.
Thus low traffic ap
I am very interested in this also. There are features of the Patch
I'd really like to use, but I keep hearing that startup times (for new
machine instantiations, which we all know happens quite frequently)
are significantly higher than bundled Django, which in turn are
significantly higher than u
Hi Andy,
On Aug 14, 7:05 pm, Andy wrote:
> I've not compared appengine-patch and google-app-engine-django for
> performance but when using google-app-engine-django r86 (which used
> django 1.0 via zipimport) I was getting a high-cpu warning for every
> second or third page load and for each of t
Hi Waldemar
I've not compared appengine-patch and google-app-engine-django for
performance but when using google-app-engine-django r86 (which used
django 1.0 via zipimport) I was getting a high-cpu warning for every
second or third page load and for each of these pages the logs showed
that zipimp
Hi Andy,
On Aug 14, 2:50 pm, Andy wrote:
> Also, the project I am working on has a very low usage pattern. It is
> written for my friend's electrical contracting company and there's
> only 3 of them! This results in zipimport being used a lot and
> negatively affecting application response times
Holger
The project I am working on was originally developed under appengine-
patch. I ported it to google-app-engine-django when I came across an
issue with appengine-patch which took quite some time to resolve. To
be fair to the appengine-patch project issue has now been fixed but I
would still
Hi Andy,
you are right, appenginepatch has got a lot of additional features.
If you don't need them, simply switch them off, as explained in the
manual:
'The Media Generator is pre-configured ... You can disable it by
removing "mediautils" from your INSTALLED_APPS. '
http://code.google.com/p/a
Hi Holger, I'm aware of the appengine patch project. It's a very
impressive bit of work but it comes with a whole bunch of extra's
included (such as the media generator).
I like google-app-engine-django for it's simplicity, which is why I am
asking about the status of the project.
Andy
On Aug 13
> it also allows you to use many other features of
> django such as application structure, development utilities
> (manage.py), django's memcached based caching and a whole bunch of
> other good stuff.
Such features are available live even for Django 1.1
http://aep-sample.appspot.com/
After codi
Hello Ian
The google-app-engine-django project does rather more than simply
making the django-1.0 libraries available under GAE, which is what the
1.2.3 update did, it also allows you to use many other features of
django such as application structure, development utilities
(manage.py), django's m
Concern the project too
2009/8/12 Ian Lewis
>
> Andy,
>
> I believe the project's goal was to support django 1.0 on appengine
> but since 1.0 is now available there isn't much point to continuing
> the project. I think that the appengine folks plan to have django
> available on appengine without
Andy,
I believe the project's goal was to support django 1.0 on appengine
but since 1.0 is now available there isn't much point to continuing
the project. I think that the appengine folks plan to have django
available on appengine without using google-app-engine-django
Ian
On Wed, Aug 12, 2009
You should be able to use dev_appserver.py rather than manage.py when
running locally without running into any errors to work around the
issue. e.g.
manage.py runserver /path/to/my/app
Becomes:
dev_appserver.py --datastore_path=/path/to/my/datastore /path/to/my/
app
It may be worth filing
Hmmm, I'm at this again and unfortunately I can't get the helper form
SVN to work at all.
All I get is:
Traceback (most recent call last):
File "manage.py", line 18, in
InstallAppengineHelperForDjango()
File "/home/jestelle/django/projects/mysite/appengine_django/
__init__.py", line 451,
Thanks Matt.
I'll try using the helper directly from svn.
Cheers,
Josh
On Sep 22, 1:44 am, Matt Brown <[EMAIL PROTECTED]> wrote:
> Aral Balkan wrote:
> > Can someone respond as to the roadmap for Django 1.0 compatibility?
>
> The currently released version of the helper (r52) supports Django 0
Aral Balkan wrote:
> Can someone respond as to the roadmap for Django 1.0 compatibility?
The currently released version of the helper (r52) supports Django 0.96
and the early Django 1.0 alpha versions.
Support for Django 1.0 final is present in the HEAD (r60) of the helper.
I'd like to add su
App Engine Patch works fine with Django 1.0
http://code.google.com/p/app-engine-patch/
On Sep 22, 9:28 am, Aral Balkan <[EMAIL PROTECTED]> wrote:
> I was thinking of updating to the latest versions of Django and the
> helper but will be holding off based on these issues.
>
> Can someone respond a
I was thinking of updating to the latest versions of Django and the
helper but will be holding off based on these issues.
Can someone respond as to the roadmap for Django 1.0 compatibility?
Thanks,
Aral
On Sep 21, 9:46 pm, Josh <[EMAIL PROTECTED]> wrote:
> I believe I was able to solve this pro
I believe I was able to solve this problem by syncing my django
install to revision 8250'ish. Using that version these obvious errors
go away... I just don't get to use the newest (best?) release of
django.
On Sep 20, 3:46 pm, Josh <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I've been following t
19 matches
Mail list logo
