Closed GoogleCodeExporter closed 9 years ago
Sorry, I can't. :(
First of all, the next step is to support Django 1.1 when it's released. If I
remove
Django you can forget Django 1.1 until Google decides to provide the next
update
which can take a very very long time...
Finally, our Django version contains a lot of patches (it's a much more
complete port
than django-helper) and monkey-patching (as it's done by django-helper and
early app-
engine-patch releases) is not an option, anymore, because it takes too much
work to
maintain everything and it's far too easy to make mistakes and introduce bugs.
At the
current level, monkey-patching would mean that I'd have to copy 1/5th of Django
into
app-engine-patch, so in the end, there would be a lot of unnecessary module
loads.
Finally, I'm not convinced that using the integrated Django version in App
Engine
will provide any speedups. Unless Google pre-loads those modules (which they
surely
won't due to their RAM requirements) you have to load them manually, anyway.
So, the
only advantage of the integrated Django version is that you don't have to so
many
files, but that's a minor issue because Google will soon raise the limit to
3000
files and since Django is zipped there aren't that many required files outside
of the
zip file, anyway (e.g., you can delete most of Django's locales in the
django_aep_export folder).
Original comment by wkornew...@gmail.com
on 19 Jun 2009 at 6:32
I am aware the importance of your project, in fact I'm going to keep using it
in the
future. I guess here is my point: zipimport is a big cpu time consumer, can we
somehow work around and take advantage of the Django version provided by GAE so
that
we can save ourselves from bearing the zipimport thing?
Original comment by DaNmarner
on 23 Jun 2009 at 7:35
Unfortunately, that's not possible. You can, however, try an unzipped Django
version.
But when I tested it, the unzipped version was not faster than the zipped
version
(though, I don't know if it consumed less ressources).
Original comment by wkornew...@gmail.com
on 23 Jun 2009 at 8:55
Original issue reported on code.google.com by
DaNmarner
on 19 Jun 2009 at 12:14