[google-appengine] Re: Django 1.0
On 8 Mai, 01:41, little_pea wrote: > Does enybody know id Django 1.0 support is planned for App Engine? If you want an easy way to use Django 1.0 (and 1.1) you can use app- engine-patch: http://code.google.com/p/app-engine-patch/ Bye, Waldemar Kornewald --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0
Note that Django 1.1 is coming "soon" ( http://www.djangoproject.com/weblog/2009/may/07/django-1-1-update/ ) so it would be nice if app engine made the leap. On May 8, 5:33 am, Andy Freeman wrote: > Native django 1.0 may not be on the roadmap, but it is a very popular > request. > > To join that crowd, > starhttp://code.google.com/p/googleappengine/issues/detail?id=872 > . > > On May 8, 1:59 am, "Nick Johnson (Google)" > wrote: > > > > > Hi little_pea, > > > It's not currently on our roadmap, so don't count on it in the near > > future. You can use Django 1.0 in your App Engine apps, you just have > > to bundle it and upload it with your app. > > > -Nick Johnson > > > On Fri, May 8, 2009 at 12:41 AM, little_pea > > wrote: > > > > Does enybody know id Django 1.0 support is planned for App Engine?- Hide > > > quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0
Native django 1.0 may not be on the roadmap, but it is a very popular request. To join that crowd, star http://code.google.com/p/googleappengine/issues/detail?id=872 . On May 8, 1:59 am, "Nick Johnson (Google)" wrote: > Hi little_pea, > > It's not currently on our roadmap, so don't count on it in the near > future. You can use Django 1.0 in your App Engine apps, you just have > to bundle it and upload it with your app. > > -Nick Johnson > > > > On Fri, May 8, 2009 at 12:41 AM, little_pea > wrote: > > > Does enybody know id Django 1.0 support is planned for App Engine?- Hide > > quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0
Hi little_pea, It's not currently on our roadmap, so don't count on it in the near future. You can use Django 1.0 in your App Engine apps, you just have to bundle it and upload it with your app. -Nick Johnson On Fri, May 8, 2009 at 12:41 AM, little_pea wrote: > > Does enybody know id Django 1.0 support is planned for App Engine? --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 + app-engine-patch
It looks like you really are missing the PIL module. syncdb isn't necessary with app-engine-patch. But, $ python manage.py shell will probably fail with the same error until PIL gets installed. Which platform are you developing on? On Jan 30, 10:44 am, metametagirl wrote: > I'm trying to start a new app using Django 1.0 with the app-engine- > patch. I'm used to using MySQL but I'm new to this datastore. The > Django tutorial says to run 'python manage.py syncdb' to create the > tables, but this doesn't work for me in my development environment. > Is this step necessary when using this combination of technologies > (Django 1.0 + app-engine-patch)? > > Also, how do you invoke the Django admin in the development > environment? My understanding is that it won't work once you upload > the app to GAE, but that there should be a way to make it work in the > dev environment. > > > python manage.py syncdb > > WARNING:root:Could not read datastore data from /var/folders/bz/ > bzgZyG4mE5adBq+imZYFdk+++TI/-Tmp-/django_myapp.datastore > WARNING:root:Could not initialize images API; you are likely missing > the Python "PIL" module. ImportError: No module named PIL > Unknown command: 'syncdb' > Type 'manage.py help' for usage. > > Thanks in advance, > Kelly --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 + app-engine-patch
Hi Kelly,
in principle, the Django admin is just a very big Django app that
provides you with a nice web-interface to edit the data in your
database.
That is also the reason that it is relatively hard to port it to App
Engine, since the database is very different here.
However, App Engine provides the so-called Administration Console,
which offers a Data Viewer.
With this Data Viewer you can also edit data in your database.
Once you have uploaded an application ("python manage.py update" in
app-engine-patch, don't forget to set your app-id in app.yaml), you
can access the Administration Console by browsing to
http://appengine.google.com/
To be fair, the Django Admin offers much more possibilities than the
Data Viewer, and is also much more advanced in regards to
customizability. Therefor a lot of people are looking forward to a
complete implementation of the Django admin on App Engine.
But since it's only a (very advanced) Django app, you can re-create
the functionality you need yourself, and it is very possible to write
your app without using the admin.
If you have just started to learn Django, I recommend the "learning by
doing" approach, since it's not really hard to use it once you have
learned the basic principles.
You can find some Django sites with complete source code here:
http://www.djangosites.org/
If you are planning to use Django on App Engine, I would recommend to
get the app-engine-patch sample project and adjust it. The only real
difference to normal Django is the model definitions.
Jesaja
On Fri, Jan 30, 2009 at 11:36 PM, metametagirl wrote:
>
> Hi Jesaja,
>
> Thanks for the explanation. Since I'm trying to do Django 1.0 on GAE,
> it's not always clear to me when to stop doing the steps in the Django
> tutorials (i.e. when it says to do 'python manage.py syncdb'.
>
> This also explains why the app-engine-patch docs say certain
> django.contrib apps a re only "available in repository". I didn't
> know what repository the doc was referring to, since I didn't realize
> you could download revisions directly from the repository. I prefer
> to use revisions that are not still under development so I guess I'll
> be skipping the admin functionality until I really need it. (At this
> beginning stage, it is not entirely clear to me what the admin
> functions are, but hopefully that will become clearer to me soon)
>
> Thanks again,
> Kelly
>
>
> On Jan 30, 1:51 pm, Jesaja Everling wrote:
>> Hi Kelly!
>>
>> You don't need the syncdb command with app-engine-patch, since unlike
>> mysql, the necessary datastore "tables" will be created on the fly.
>> I haven't really used the admin in app-engine-patch myself yet, but I
>> have seen it work in the sample project that is provided with
>> app-engine-patch.
>> To use the admin, however, you must use the repository version of
>> app-engine-patch, the latest release doesn't yet include the admin.
>> When you click the "Source" tab on the project page, you will find a
>> link to the different Mercurial repositories that app-engine-patch
>> uses.
>>
>> http://code.google.com/p/app-engine-patch/wiki/GettingTheSource?tm=4
>>
>> You will probably want to check out the sample project. You can either
>> install a Mercurial client and clone the repository, or can use the
>> download-option that bitbucket provides.
>> Be aware, however, that you are using a version that is under constant
>> development now, so things might break when introducing new features,
>> or some things may be incomplete.
>>
>> Best Regards,
>>
>> Jesaja Everling
>>
>> On Fri, Jan 30, 2009 at 7:44 PM, metametagirl wrote:
>>
>> > I'm trying to start a new app using Django 1.0 with the app-engine-
>> > patch. I'm used to using MySQL but I'm new to this datastore. The
>> > Django tutorial says to run 'python manage.py syncdb' to create the
>> > tables, but this doesn't work for me in my development environment.
>> > Is this step necessary when using this combination of technologies
>> > (Django 1.0 + app-engine-patch)?
>>
>> > Also, how do you invoke the Django admin in the development
>> > environment? My understanding is that it won't work once you upload
>> > the app to GAE, but that there should be a way to make it work in the
>> > dev environment.
>>
>> >> python manage.py syncdb
>> > WARNING:root:Could not read datastore data from /var/folders/bz/
>> > bzgZyG4mE5adBq+imZYFdk+++TI/-Tmp-/django_myapp.datastore
>> > WARNING:root:Could not initialize images API; you are likely missing
>> > the Python "PIL" module. ImportError: No module named PIL
>> > Unknown command: 'syncdb'
>> > Type 'manage.py help' for usage.
>>
>> > Thanks in advance,
>> > Kelly
> >
>
--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For
[google-appengine] Re: Django 1.0 + app-engine-patch
Hi Jesaja, Thanks for the explanation. Since I'm trying to do Django 1.0 on GAE, it's not always clear to me when to stop doing the steps in the Django tutorials (i.e. when it says to do 'python manage.py syncdb'. This also explains why the app-engine-patch docs say certain django.contrib apps a re only "available in repository". I didn't know what repository the doc was referring to, since I didn't realize you could download revisions directly from the repository. I prefer to use revisions that are not still under development so I guess I'll be skipping the admin functionality until I really need it. (At this beginning stage, it is not entirely clear to me what the admin functions are, but hopefully that will become clearer to me soon) Thanks again, Kelly On Jan 30, 1:51 pm, Jesaja Everling wrote: > Hi Kelly! > > You don't need the syncdb command with app-engine-patch, since unlike > mysql, the necessary datastore "tables" will be created on the fly. > I haven't really used the admin in app-engine-patch myself yet, but I > have seen it work in the sample project that is provided with > app-engine-patch. > To use the admin, however, you must use the repository version of > app-engine-patch, the latest release doesn't yet include the admin. > When you click the "Source" tab on the project page, you will find a > link to the different Mercurial repositories that app-engine-patch > uses. > > http://code.google.com/p/app-engine-patch/wiki/GettingTheSource?tm=4 > > You will probably want to check out the sample project. You can either > install a Mercurial client and clone the repository, or can use the > download-option that bitbucket provides. > Be aware, however, that you are using a version that is under constant > development now, so things might break when introducing new features, > or some things may be incomplete. > > Best Regards, > > Jesaja Everling > > On Fri, Jan 30, 2009 at 7:44 PM, metametagirl wrote: > > > I'm trying to start a new app using Django 1.0 with the app-engine- > > patch. I'm used to using MySQL but I'm new to this datastore. The > > Django tutorial says to run 'python manage.py syncdb' to create the > > tables, but this doesn't work for me in my development environment. > > Is this step necessary when using this combination of technologies > > (Django 1.0 + app-engine-patch)? > > > Also, how do you invoke the Django admin in the development > > environment? My understanding is that it won't work once you upload > > the app to GAE, but that there should be a way to make it work in the > > dev environment. > > >> python manage.py syncdb > > WARNING:root:Could not read datastore data from /var/folders/bz/ > > bzgZyG4mE5adBq+imZYFdk+++TI/-Tmp-/django_myapp.datastore > > WARNING:root:Could not initialize images API; you are likely missing > > the Python "PIL" module. ImportError: No module named PIL > > Unknown command: 'syncdb' > > Type 'manage.py help' for usage. > > > Thanks in advance, > > Kelly --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 + app-engine-patch
Hi Kelly! You don't need the syncdb command with app-engine-patch, since unlike mysql, the necessary datastore "tables" will be created on the fly. I haven't really used the admin in app-engine-patch myself yet, but I have seen it work in the sample project that is provided with app-engine-patch. To use the admin, however, you must use the repository version of app-engine-patch, the latest release doesn't yet include the admin. When you click the "Source" tab on the project page, you will find a link to the different Mercurial repositories that app-engine-patch uses. http://code.google.com/p/app-engine-patch/wiki/GettingTheSource?tm=4 You will probably want to check out the sample project. You can either install a Mercurial client and clone the repository, or can use the download-option that bitbucket provides. Be aware, however, that you are using a version that is under constant development now, so things might break when introducing new features, or some things may be incomplete. Best Regards, Jesaja Everling On Fri, Jan 30, 2009 at 7:44 PM, metametagirl wrote: > > I'm trying to start a new app using Django 1.0 with the app-engine- > patch. I'm used to using MySQL but I'm new to this datastore. The > Django tutorial says to run 'python manage.py syncdb' to create the > tables, but this doesn't work for me in my development environment. > Is this step necessary when using this combination of technologies > (Django 1.0 + app-engine-patch)? > > Also, how do you invoke the Django admin in the development > environment? My understanding is that it won't work once you upload > the app to GAE, but that there should be a way to make it work in the > dev environment. > >> python manage.py syncdb > WARNING:root:Could not read datastore data from /var/folders/bz/ > bzgZyG4mE5adBq+imZYFdk+++TI/-Tmp-/django_myapp.datastore > WARNING:root:Could not initialize images API; you are likely missing > the Python "PIL" module. ImportError: No module named PIL > Unknown command: 'syncdb' > Type 'manage.py help' for usage. > > Thanks in advance, > Kelly > > > > --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 - any update on plans to replace 0.96 ?
It will be nice if GAE always keep one warmed up spare process. On Dec 12, 4:47 pm, "Sharp-Developer.Net" wrote: > Thanks Marzia, > > Have GAE team thought about providing some "warm-up" url? > > So if GAE see a load is increasing > (and probably could predict a new request handler will be needed soon) > then engine calls some URL specified in app.yaml (for example) and > a request handler instance created and kept in cache for a while. > > So we do not waste time when a user request comes? > > I do not talk about 100% accuracy but some sort of pro-active warming > would benefit. > > May be you could even disable calls to DB/memcache/etc so it is just > modules initialization. > -- > Alexhttp://sharp-developer.net/ > > On Dec 12, 6:49 pm, Marzia Niccolai wrote: > > > Hi Alex, > > > We are definitely interested in offering Django 1.0 with App Engine in the > > future. However, it seems likely that including Django 1.0 as the default > > Django version with App Engine would need to be part of an api version > > change, since such a change would likely brake existing apps. > > > In terms of the high CPU warnings, we are generally working on a solution > > that will lesson the affect of such warnings on applications, so we hope we > > can address this soon not just for this case, but in general. > > > As for the time concern, there isn't much right now that can be done. But > > as your application increases in popularity, it's more likely people will > > see an already warm interpreter and thus not have to wait for a new > > initialization. > > > -Marzia > > > On Fri, Dec 12, 2008 at 6:14 AM, Sharp-Developer.Net < > > > alexander.trakhime...@gmail.com> wrote: > > > > Hi, > > > > Any plans to update Django 0.96 to Django 1.0 ? > > > > The 1.0 has been released on Sep 3 and still not there. > > > > I use local version of Django 1.0 and it's OK but my concern is > > > performance and CPU usage. > > > > Whenever new instance of handler is created by GAE it takes some time > > > and I guess CPU cycles. > > > > I've noticed Django loading and appengine_django helper installation > > > takes solid amount of time (~0.8 sec) and I guess CPU cycles. > > > > See log extract from "main.py" : > > > > > > # 12-11 10:42AM 27.040 - Loading django helper... > > > # 12-11 10:42AM 27.862 - Successfully loaded django helper > > > > > > > It does not affect my CPU quota but harm user expirience and make me > > > nervous when checking logs in admin console :). > > > > I assume if we load Django provided by GAE it will be pre-loaded and > > > thus no CPU/time penalities for app. Is my assumption correct? > > > > Would be really great if we could get the Django version 1.0 provided > > > by default. > > > > The latest reply on this is > > >http://groups.google.com/group/google-appengine/msg/c3bb71cd63d8d32f > > > > May be we should fill a feature request to speed it up? > > > > P.S. I'm wonder what if Django could be provided pre-patched as an > > > option? > > > > P.P.S. I know - this is too specific request for general platform as > > > GAE so would be happy to get any advises on speeding up "cold" > > > requests. For example I already do not load Django if page content > > > found in memcache. Still would prefer to have Django pre-loaded. May > > > be by specifying this in app.yaml? > > > -- > > > Alex > > > http:/sharp-developer.net/ --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 - any update on plans to replace 0.96 ?
For the time being I've disabled some operations in InstallAppengineHelperForDjango() (which I believe not used by my app at the moment) That reduced init time of Django from 0.8 to 0.3 sec. LoadAppengineEnvironment() #InstallReplacementImpModule() InstallAppengineDatabaseBackend() InstallModelForm() #InstallGoogleMemcache() InstallDjangoModuleReplacements() #PatchDjangoSerializationModules() CleanupDjangoSettings() #ModifyAvailableCommands() #InstallGoogleSMTPConnection() #InstallAuthentication() May be it could be useful to someone. Have fun. -- Alex http://sharp-developer.net/ On Dec 12, 9:47 pm, "Sharp-Developer.Net" wrote: > Thanks Marzia, > > Have GAE team thought about providing some "warm-up" url? > > So if GAE see a load is increasing > (and probably could predict a new request handler will be needed soon) > then engine calls some URL specified in app.yaml (for example) and > a request handler instance created and kept in cache for a while. > > So we do not waste time when a user request comes? > > I do not talk about 100% accuracy but some sort of pro-active warming > would benefit. > > May be you could even disable calls to DB/memcache/etc so it is just > modules initialization. > -- > Alexhttp://sharp-developer.net/ > > On Dec 12, 6:49 pm, Marzia Niccolai wrote: > > > Hi Alex, > > > We are definitely interested in offering Django 1.0 with App Engine in the > > future. However, it seems likely that including Django 1.0 as the default > > Django version with App Engine would need to be part of an api version > > change, since such a change would likely brake existing apps. > > > In terms of the high CPU warnings, we are generally working on a solution > > that will lesson the affect of such warnings on applications, so we hope we > > can address this soon not just for this case, but in general. > > > As for the time concern, there isn't much right now that can be done. But > > as your application increases in popularity, it's more likely people will > > see an already warm interpreter and thus not have to wait for a new > > initialization. > > > -Marzia > > > On Fri, Dec 12, 2008 at 6:14 AM, Sharp-Developer.Net < > > > alexander.trakhime...@gmail.com> wrote: > > > > Hi, > > > > Any plans to update Django 0.96 to Django 1.0 ? > > > > The 1.0 has been released on Sep 3 and still not there. > > > > I use local version of Django 1.0 and it's OK but my concern is > > > performance and CPU usage. > > > > Whenever new instance of handler is created by GAE it takes some time > > > and I guess CPU cycles. > > > > I've noticed Django loading and appengine_django helper installation > > > takes solid amount of time (~0.8 sec) and I guess CPU cycles. > > > > See log extract from "main.py" : > > > > > > # 12-11 10:42AM 27.040 - Loading django helper... > > > # 12-11 10:42AM 27.862 - Successfully loaded django helper > > > > > > > It does not affect my CPU quota but harm user expirience and make me > > > nervous when checking logs in admin console :). > > > > I assume if we load Django provided by GAE it will be pre-loaded and > > > thus no CPU/time penalities for app. Is my assumption correct? > > > > Would be really great if we could get the Django version 1.0 provided > > > by default. > > > > The latest reply on this is > > >http://groups.google.com/group/google-appengine/msg/c3bb71cd63d8d32f > > > > May be we should fill a feature request to speed it up? > > > > P.S. I'm wonder what if Django could be provided pre-patched as an > > > option? > > > > P.P.S. I know - this is too specific request for general platform as > > > GAE so would be happy to get any advises on speeding up "cold" > > > requests. For example I already do not load Django if page content > > > found in memcache. Still would prefer to have Django pre-loaded. May > > > be by specifying this in app.yaml? > > > -- > > > Alex > > > http:/sharp-developer.net/ > > --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 - any update on plans to replace 0.96 ?
Thanks Marzia, Have GAE team thought about providing some "warm-up" url? So if GAE see a load is increasing (and probably could predict a new request handler will be needed soon) then engine calls some URL specified in app.yaml (for example) and a request handler instance created and kept in cache for a while. So we do not waste time when a user request comes? I do not talk about 100% accuracy but some sort of pro-active warming would benefit. May be you could even disable calls to DB/memcache/etc so it is just modules initialization. -- Alex http://sharp-developer.net/ On Dec 12, 6:49 pm, Marzia Niccolai wrote: > Hi Alex, > > We are definitely interested in offering Django 1.0 with App Engine in the > future. However, it seems likely that including Django 1.0 as the default > Django version with App Engine would need to be part of an api version > change, since such a change would likely brake existing apps. > > In terms of the high CPU warnings, we are generally working on a solution > that will lesson the affect of such warnings on applications, so we hope we > can address this soon not just for this case, but in general. > > As for the time concern, there isn't much right now that can be done. But > as your application increases in popularity, it's more likely people will > see an already warm interpreter and thus not have to wait for a new > initialization. > > -Marzia > > On Fri, Dec 12, 2008 at 6:14 AM, Sharp-Developer.Net < > > alexander.trakhime...@gmail.com> wrote: > > > Hi, > > > Any plans to update Django 0.96 to Django 1.0 ? > > > The 1.0 has been released on Sep 3 and still not there. > > > I use local version of Django 1.0 and it's OK but my concern is > > performance and CPU usage. > > > Whenever new instance of handler is created by GAE it takes some time > > and I guess CPU cycles. > > > I've noticed Django loading and appengine_django helper installation > > takes solid amount of time (~0.8 sec) and I guess CPU cycles. > > > See log extract from "main.py" : > > > > # 12-11 10:42AM 27.040 - Loading django helper... > > # 12-11 10:42AM 27.862 - Successfully loaded django helper > > > > > It does not affect my CPU quota but harm user expirience and make me > > nervous when checking logs in admin console :). > > > I assume if we load Django provided by GAE it will be pre-loaded and > > thus no CPU/time penalities for app. Is my assumption correct? > > > Would be really great if we could get the Django version 1.0 provided > > by default. > > > The latest reply on this is > >http://groups.google.com/group/google-appengine/msg/c3bb71cd63d8d32f > > > May be we should fill a feature request to speed it up? > > > P.S. I'm wonder what if Django could be provided pre-patched as an > > option? > > > P.P.S. I know - this is too specific request for general platform as > > GAE so would be happy to get any advises on speeding up "cold" > > requests. For example I already do not load Django if page content > > found in memcache. Still would prefer to have Django pre-loaded. May > > be by specifying this in app.yaml? > > -- > > Alex > > http:/sharp-developer.net/ > > --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 - any update on plans to replace 0.96 ?
Hi Alex, We are definitely interested in offering Django 1.0 with App Engine in the future. However, it seems likely that including Django 1.0 as the default Django version with App Engine would need to be part of an api version change, since such a change would likely brake existing apps. In terms of the high CPU warnings, we are generally working on a solution that will lesson the affect of such warnings on applications, so we hope we can address this soon not just for this case, but in general. As for the time concern, there isn't much right now that can be done. But as your application increases in popularity, it's more likely people will see an already warm interpreter and thus not have to wait for a new initialization. -Marzia On Fri, Dec 12, 2008 at 6:14 AM, Sharp-Developer.Net < alexander.trakhime...@gmail.com> wrote: > > Hi, > > Any plans to update Django 0.96 to Django 1.0 ? > > The 1.0 has been released on Sep 3 and still not there. > > I use local version of Django 1.0 and it's OK but my concern is > performance and CPU usage. > > Whenever new instance of handler is created by GAE it takes some time > and I guess CPU cycles. > > I've noticed Django loading and appengine_django helper installation > takes solid amount of time (~0.8 sec) and I guess CPU cycles. > > See log extract from "main.py" : > > # 12-11 10:42AM 27.040 - Loading django helper... > # 12-11 10:42AM 27.862 - Successfully loaded django helper > > > It does not affect my CPU quota but harm user expirience and make me > nervous when checking logs in admin console :). > > I assume if we load Django provided by GAE it will be pre-loaded and > thus no CPU/time penalities for app. Is my assumption correct? > > Would be really great if we could get the Django version 1.0 provided > by default. > > The latest reply on this is > http://groups.google.com/group/google-appengine/msg/c3bb71cd63d8d32f > > May be we should fill a feature request to speed it up? > > P.S. I'm wonder what if Django could be provided pre-patched as an > option? > > P.P.S. I know - this is too specific request for general platform as > GAE so would be happy to get any advises on speeding up "cold" > requests. For example I already do not load Django if page content > found in memcache. Still would prefer to have Django pre-loaded. May > be by specifying this in app.yaml? > -- > Alex > http:/sharp-developer.net/ > > > --~--~-~--~~~---~--~~ 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-appengine@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: Django 1.0 -- would someone from Google please respond
Paul, Thanks very much for answering my question, I really appreciate it and I am sure many others do as well. Thanks again, Michael I Angerman Albuquerque, New Mexico http://www.zrato.com On Mon, Sep 8, 2008 at 4:14 PM, Paul <[EMAIL PROTECTED]> wrote: > > Hi Michael, > > While we'd like to support Django 1.0 be default in App Engine its > going to be a little while before we'll have that support. We are > currently working on some larger features that require the team's > resources. For the time being we suggest you include it in the app you > are uploading to App Engine. Below is a link to a thread that discuss > getting Django 1.0 working with App Engine. > > > http://groups.google.com/group/google-appengine/browse_thread/thread/edaa3f36ebef201f/a0935973b63b9e34?lnk=gst&q=Using+django+1.0#a0935973b63b9e34 > > Please let us know if you have any questions. > > Paul - Product Manager, App Engine > > On Sep 6, 12:35 pm, "Michael Angerman" <[EMAIL PROTECTED]> wrote: > > If this group has already got an official announcement that the next > version > > of appengine > > will have Django 1.0 inside it, so we don't have to upload it with our > app, > > > > Just tell me its official and point me to the email or blog posting where > it > > has been announced, > > if it hasn't been announced yet then here goes my flame. > > > > There are lots of developers out there in the community who would like to > > know the answer > > to this question, because it impacts them on whether or not to release > their > > new app or lets say > > wait for another week or two. > > > > This is exactly the type of communication that is lacking from Google's > > management -- and why > > their has been a thread recently on why people are disappointed in the > lack > > of information from Google. > > > > I think appengine is a great product, really amazing, and I think all of > the > > other Google products are great > > too, so I am big huge fan of Google, but why are they letting the > developer > > community down by not supplying > > them with information in a timely fashion that impacts developers > decisions. > > > > This information that I am asking for is extremely basic and others have > > asked the same question in recent days. > > > > So I could go on here, but Google management ! surprise us for once and > > just answer the question definitively. > > I am not expecting to have an answer like it will happen next week. But > > just give the developer community a > > general sense that yes it will happen in the next month or so, or not, > that > > is sort of OK too, but keeping the > > community abreast on what is going on is really the point here. > > > > Thanks for you continued support, > > > > Michael I Angerman > > Albuquerque, New Mexico > > > > http://www.zrato.com > > > --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django 1.0 -- would someone from Google please respond
On Mon, Sep 8, 2008 at 6:14 PM, Paul <[EMAIL PROTECTED]> wrote: > > Hi Michael, > > While we'd like to support Django 1.0 be default in App Engine its > going to be a little while before we'll have that support. Paul, I would like to point out that there is also very heavy demand for other web frameworks in addition to Django. Currently appengine comes bundled with WebOb, which is a core library that Turbogears 2.0 and Pylons use. There is a substantial base of professional software developers all of the world that would love to have Django as well as WebOb derived frameworks bundled. Personally, I think it would be a great service to the Python community to natively include these frameworks with appengine if Django is included, or at least ensure that their components work such as Genshi or Mako templating by default. Thanks again for the communication! We are > currently working on some larger features that require the team's > resources. For the time being we suggest you include it in the app you > are uploading to App Engine. Below is a link to a thread that discuss > getting Django 1.0 working with App Engine. > > http://groups.google.com/group/google-appengine/browse_thread/thread/edaa3f36ebef201f/a0935973b63b9e34?lnk=gst&q=Using+django+1.0#a0935973b63b9e34 > > Please let us know if you have any questions. > > Paul - Product Manager, App Engine > > On Sep 6, 12:35 pm, "Michael Angerman" <[EMAIL PROTECTED]> wrote: >> If this group has already got an official announcement that the next version >> of appengine >> will have Django 1.0 inside it, so we don't have to upload it with our app, >> >> Just tell me its official and point me to the email or blog posting where it >> has been announced, >> if it hasn't been announced yet then here goes my flame. >> >> There are lots of developers out there in the community who would like to >> know the answer >> to this question, because it impacts them on whether or not to release their >> new app or lets say >> wait for another week or two. >> >> This is exactly the type of communication that is lacking from Google's >> management -- and why >> their has been a thread recently on why people are disappointed in the lack >> of information from Google. >> >> I think appengine is a great product, really amazing, and I think all of the >> other Google products are great >> too, so I am big huge fan of Google, but why are they letting the developer >> community down by not supplying >> them with information in a timely fashion that impacts developers decisions. >> >> This information that I am asking for is extremely basic and others have >> asked the same question in recent days. >> >> So I could go on here, but Google management ! surprise us for once and >> just answer the question definitively. >> I am not expecting to have an answer like it will happen next week. But >> just give the developer community a >> general sense that yes it will happen in the next month or so, or not, that >> is sort of OK too, but keeping the >> community abreast on what is going on is really the point here. >> >> Thanks for you continued support, >> >> Michael I Angerman >> Albuquerque, New Mexico >> >> http://www.zrato.com > > > -- Noah Gift http://noahgift.com --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django 1.0 -- would someone from Google please respond
Hi Michael, While we'd like to support Django 1.0 be default in App Engine its going to be a little while before we'll have that support. We are currently working on some larger features that require the team's resources. For the time being we suggest you include it in the app you are uploading to App Engine. Below is a link to a thread that discuss getting Django 1.0 working with App Engine. http://groups.google.com/group/google-appengine/browse_thread/thread/edaa3f36ebef201f/a0935973b63b9e34?lnk=gst&q=Using+django+1.0#a0935973b63b9e34 Please let us know if you have any questions. Paul - Product Manager, App Engine On Sep 6, 12:35 pm, "Michael Angerman" <[EMAIL PROTECTED]> wrote: > If this group has already got an official announcement that the next version > of appengine > will have Django 1.0 inside it, so we don't have to upload it with our app, > > Just tell me its official and point me to the email or blog posting where it > has been announced, > if it hasn't been announced yet then here goes my flame. > > There are lots of developers out there in the community who would like to > know the answer > to this question, because it impacts them on whether or not to release their > new app or lets say > wait for another week or two. > > This is exactly the type of communication that is lacking from Google's > management -- and why > their has been a thread recently on why people are disappointed in the lack > of information from Google. > > I think appengine is a great product, really amazing, and I think all of the > other Google products are great > too, so I am big huge fan of Google, but why are they letting the developer > community down by not supplying > them with information in a timely fashion that impacts developers decisions. > > This information that I am asking for is extremely basic and others have > asked the same question in recent days. > > So I could go on here, but Google management ! surprise us for once and > just answer the question definitively. > I am not expecting to have an answer like it will happen next week. But > just give the developer community a > general sense that yes it will happen in the next month or so, or not, that > is sort of OK too, but keeping the > community abreast on what is going on is really the point here. > > Thanks for you continued support, > > Michael I Angerman > Albuquerque, New Mexico > > http://www.zrato.com --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django 1.0?
Very Good :-) ***NEWS*** Jython compatibility http://docs.djangoproject.com/en/dev/howto/jython/#howto-jython ***ISSUES*** Caveats with support of certain databases http://docs.djangoproject.com/en/dev/ref/databases/#mysql-notes http://docs.djangoproject.com/en/dev/ref/databases/#sqlite-notes http://docs.djangoproject.com/en/dev/ref/databases/#oracle-notes -- Best Template Engine http://pyoohtml.appspot.com/best-template-engine On Sep 5, 5:29 am, Alexander Kojevnikov <[EMAIL PROTECTED]> wrote: > > What are the new features of Django? > > http://docs.djangoproject.com/en/dev/releases/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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django 1.0?
> What are the new features of Django? http://docs.djangoproject.com/en/dev/releases/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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django 1.0?
What are the new features of Django? -- Best Template Engine http://pyoohtml.appspot.com/best-template-engine On Sep 4, 6:07 am, Nico <[EMAIL PROTECTED]> wrote: > I think the question is not if, but when. > I hope it will happen very soon, now that 1.0 final is out... > > On 4 Sep., 02:40, DaNmarner <[EMAIL PROTECTED]> wrote: > > > Does any body know whether GAE is going to update the version included > > Django to 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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django 1.0?
I think the question is not if, but when. I hope it will happen very soon, now that 1.0 final is out... On 4 Sep., 02:40, DaNmarner <[EMAIL PROTECTED]> wrote: > Does any body know whether GAE is going to update the version included > Django to 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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django 1.0?
First search result on "Django 1.0": http://groups.google.com/group/google-appengine/msg/d91a710891cc6789 On Sep 3, 8:40 pm, DaNmarner <[EMAIL PROTECTED]> wrote: > Does any body know whether GAE is going to update the version included > Django to 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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
