[google-appengine] App stops working after entity delete django 1.2 issue

[todu]

Not sure if others have the same issue.  After I deleted an entitty or 
tried to copy it to another app I started getting  with my whole app not 
working Seems like the whole django 1.2 thing continues to be messy 
 anybody have ideas?-

: django 1.2 
was requested, but 0.96.4.None is already in use
Traceback (most recent call last):
  File "/base/data/home/apps/zatobowl/1.354335995581212831/home.py", line 4, in 

use_library('django', '1.2')
  File 
"/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py", 
line 414, in use_library
InstallLibrary(name, version, explicit=True)
  File 
"/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py", 
line 367, in InstallLibrary
CheckInstalledVersion(name, version, explicit=True)
  File 
"/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py", 
line 300, in CheckInstalledVersion
(name, desired_version, installed_version))

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/on1IHphNKPwJ.
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.

Re: [google-appengine] 1.6.0 Prerelease SDKs are out

[Gopal Patel]

does python sdk now works with py2.7 ?

On Tue, Nov 1, 2011 at 6:58 AM, Johan Euphrosine  wrote:

> Hi,
>
> We've just uploaded the 1.6.0 Prerelease SDKs:
> http://code.google.com/p/googleappengine/downloads/list
>
> Please note that new features are not available in production until the
> final release, and documentation for these features will be available at
> this time as well. Let us know if there are any issues found.
>
> Below are the release notes for this release.
>
> Thanks,
> Marzia
>
> App Engine Python SDK - Release NotesVersion 
> 1.6.0===- On November 7th, App Engine will be out 
> of Preview. The new Terms of Service  and previously announced pricing 
> changes will be in effect. Additionally, all  paid apps are now covered by 
> our SLA.http://www.google.com/enterprise/cloud/appengine/pricing.html 
> -
>  Paid apps can now specify the maximum pending latency for instances and the  
> minimum number of idle instances for your application in the Admin Console.- 
> We have released an experimental utility, available in the Admin Console, to  
> assist in migrating your application to the High Replication datastore. This  
> utility allows you to copy the bulk of your data in the background, while the 
>  source application is still serving. You then need a brief read-only period 
> to  migrate your application data while you copy the data that has changed 
> from  the time the original copy started.- Blobstore, which was previously 
> limited to apps with billing enabled, is now  available for all apps.- We 
> have published a new article on Datastore Index Selection and Advanced  
> Search which explains our recent improvements to the query planner that make  
> exploding indexes unnecessary.
> http://code.google.com/appengine/articles/indexselection.html 
> -
>  Applications can now receive xmpp error stanzas at /_ah/xmpp/error.- In the 
> Admin Console data viewer, you can now filter by namespace from a drop  down 
> menu, if applicable.- In the Admin Console's Datastore Statistics, we now 
> offer namespace suggest  for filtering stats.- We have released as 
> experimental the full MapReduce framework.- The mail_stub.get_sent_messages() 
> call now returns EmailMessage instances.- Fixed an issue when setting an 
> initial_value in memcache.incr unexpectedly  returned a string.
> http://code.google.com/p/googleappengine/issues/detail?id=2012 
> -
>  Fixed an issue where DoS stats in the Admin Console didn't work for High  
> Replication apps.
> http://code.google.com/p/googleappengine/issues/detail?id=5237 
> 
>
>
>
> App Engine Java SDK - Release NotesVersion 1.6.0=- On November 
> 7th, App Engine will be out of Preview. The new Terms of Service  and 
> previously announced pricing changes will be in effect. Additionally, all  
> paid apps are now covered by our SLA.
> http://www.google.com/enterprise/cloud/appengine/pricing.html 
> -
>  Paid apps can now specify the maximum pending latency for instances and the  
> minimum number of idle instances for your application in the Admin Console.- 
> We have released an experimental utility, available in the Admin Console, to  
> assist in migrating your application to the High Replication datastore. This  
> utility allows you to copy the bulk of your data in the background, while the 
>  source application is still serving. You then need a brief read-only period 
> to  migrate your application data while you copy the data that has changed 
> from  the time the original copy started.- Blobstore, which was previously 
> limited to apps with billing enabled, is now  available for all apps.- We 
> have published a new article on Datastore Index Selection and Advanced  
> Search which explains our recent improvements to the query planner that make  
> exploding indexes unnecessary.
> http://code.google.com/appengine/articles/indexselection.html 
> -
>  Applications can now receive xmpp error stanzas at /_ah/xmpp/error.- In the 
> Admin Console data viewer, you can now filter by namespace from a drop  down 
> menu, if applicable.- In the Admin Console's Datastore Statistics, we now 
> offer namespace suggest  f

Re: [google-appengine] Re: TemplateSyntaxError: Caught ImportError while rendering: No module named http (while migrating py2.5 to py2.7 application)

[Brian Quinlan]

Hi Mariano,

You are using the Django "url" tag, which isn't supported by the
google.appengine.ext.webapp,template in the Python 2.7 runtime.

I'll try to make the error message more meaningful.

Cheers,
Brian

On Tue, Nov 1, 2011 at 11:38 AM, Brian Quinlan  wrote:
> Hi Mariano,
>
> Thanks for bringing this up. I'll take a look at the issue some time
> day and report back.
>
> Cheers,
> Brian
>
> On Mon, Oct 31, 2011 at 11:26 PM, Mariano Benitez  
> wrote:
>>
>> looking at the sources here I found this line:
>> from google.appengine._internal.django.http import Http404
>> package http is not there in the sources, but I found that class Http404 is 
>> now in django package itself here
>>
>>
>> Any help is appreciated!!!
>> Thanks,
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/google-appengine/-/ANIciPS8ikoJ.
>> 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.
>

-- 
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.

Re: [google-appengine] Early experimental release of Yaac! Which allows you execute query with aggregation functions / multiple inequality filters etc.

[Max]

Thanks Waleed for your feedback!

On Tuesday, November 1, 2011 4:16:47 AM UTC+8, Waleed wrote:
>
> I really like this project and have been hoping someone would do it for a 
> long time. The need to run arbitrary reports on the datastore is clear, and 
> the current tools are a pain. So this is a great start. My feedback:
>
> - It's still buggy. I ran a few queries and only some of them worked, and 
> the others just get stuck in processing. 
>
> As I said this is a very early release. I am sure it will be much better 
in couple of days. I checked sandbox log and It looks many queries failed 
because the result message is too big for channel service to send. Can you 
paste your query and let me double check, just to make sure this is not 
some other unknown bug.
 

> - Definitely change the name. "Yet another..." makes it feel cheap.
>
> Agree, Yet Another looks like a temp name or a demo project name. Any good 
suggestions?
 

> - I don't like the concept of running it as a separate version. I prefer 
> to drop the code in a separate folder in my project and access it with it's 
> own path (e.g. /yaac), just like appstats and mapreduce.
>
Any specific reason you want to put admin tool together with your main code 
base? How about when you only want to upgrade Yaac? 

I put this into a separate version because my major version is written in 
Go, and there are quite a lot features not supported in Go SDK yet.

What do you think?
 

>
> - I would suggest focusing on EGQL and making it really solid. Remove the 
> other features (blobstore, memcache, taskqueues...etc) to avoid 
> distractions until EGQL is robust. Expanding the scope at this early stage 
> will only spread your efforts too thin and you end up with many half-baked 
> features that no one wants to use. 
>
> Agree, the main focus is always EGQL until it's good and robust enough. I 
will be working on update / delete statement, as well as pre-query instance 
hour estimation.
 

> Good luck,
> Waleed
>
>
>
> On Mon, Oct 31, 2011 at 9:24 AM, Max  wrote:
>
>> As we all know we can not use join, aggregation functions, group by or 
>> multiple inequalities in datastore query. Google's argument is these 
>> relational feature are not scalable. But there has to be some use cases 
>> like ad hoc request to generate some report. We then have to prepare / test 
>> our own mapreduce / pipeline scripts and deploy to production environment, 
>> which is usually error prone and not trivial.
>>
>> Project Yaac(Yet Another Admin Console) is targeted to solve this common 
>> use case. Yaac is not a standalone java or python library, instead it's a 
>> complete application which is designed to be deployed to your own domain 
>> (non-default version of course). Yaac provides Extended GQL(EGQL), which 
>> supports aggregation function / group by / complex nested expressions / 
>> multiple inequality filters / *not*, *or* clause in where condition. For 
>> instance, in a football datastore, you can execute following EGQL query:
>>
>>  select HOME_TEAM, AWAY_TEAM, COUNT(1), sum(FTHG > FTAG), sum(FTHG = 
>> FTAG), sum(FTHG < FTAG) 
>>  from MATCH 
>>  where HOME_TEAM = "Arsenal" 
>>  group by HOME_TEAM, AWAY_TEAM
>>  having sum(FTHG > FTAG) > sum(FTHG = FTAG) + sum(FTHG < FTAG) 
>>
>> More details visit this page: 
>> http://code.google.com/p/yaac/wiki/EGQLReference Because it's an early 
>> experimental verion, some part of the language may subject to change in the 
>> future.
>>
>> There is also a sandbox environment 
>> http://sandbox.yetanotheradminconsole.appspot.com/. Anyone with a Google 
>> account can login and play with Sandbox. Simply go to Datastore --> 
>> Extended GQL then execute above query. I have uploaded 86000 football 
>> matches (all matches played in 10 leagues for last 18 seasons). For 
>> example, to retrieve all matches played in Arsenal's home against Man 
>> United after year 2000 and at least one teams scored in the game. We can 
>> execute following query:
>>
>> select HOME_TEAM, AWAY_TEAM, format(MATCH_DATE, "MMM dd, "), FTHG, 
>> FTAG 
>> from MATCH 
>> where HOME_TEAM = "Arsenal" and AWAY_TEAM = "Man United" and MATCH_DATE > 
>> datetime("2101") and FTHG + FTAG > 0
>>
>> (FTHG means full time home goal :) )
>>
>> It only tooks several steps to deploy Yaac to your own domain, check out 
>> http://code.google.com/p/yaac/wiki/DeployGuideline
>>  
>> Again, it's a very very early experimental release, you may notice that 
>> the performance is extremely slow. This is because all queries are executed 
>> by pipeline API in a niave way, sequential scanning over whole datastore. I 
>> will spend more time to optimize it these days.
>>
>> Please try to set batch size to a smaller value if you are not performing 
>> query with aggregation / group by, otherwise it's very easy for a result 
>> message to hit channel service single message size limit (32KB). This will 
>> also be fixed soon.
>>
>> I will also try to provide a better error / e

[google-appengine] 1.6.0 Prerelease SDKs are out

[Johan Euphrosine]

Hi,

We've just uploaded the 1.6.0 Prerelease SDKs:
http://code.google.com/p/googleappengine/downloads/list

Please note that new features are not available in production until the
final release, and documentation for these features will be available at
this time as well. Let us know if there are any issues found.

Below are the release notes for this release.

Thanks,
Marzia

App Engine Python SDK - Release NotesVersion
1.6.0===- On November 7th, App Engine will
be out of Preview. The new Terms of Service  and previously announced
pricing changes will be in effect. Additionally, all  paid apps are
now covered by our SLA.
http://www.google.com/enterprise/cloud/appengine/pricing.html
-
Paid apps can now specify the maximum pending latency for instances
and the  minimum number of idle instances for your application in the
Admin Console.- We have released an experimental utility, available in
the Admin Console, to  assist in migrating your application to the
High Replication datastore. This  utility allows you to copy the bulk
of your data in the background, while the  source application is still
serving. You then need a brief read-only period to  migrate your
application data while you copy the data that has changed from  the
time the original copy started.- Blobstore, which was previously
limited to apps with billing enabled, is now  available for all apps.-
We have published a new article on Datastore Index Selection and
Advanced  Search which explains our recent improvements to the query
planner that make  exploding indexes unnecessary.
http://code.google.com/appengine/articles/indexselection.html
-
Applications can now receive xmpp error stanzas at /_ah/xmpp/error.-
In the Admin Console data viewer, you can now filter by namespace from
a drop  down menu, if applicable.- In the Admin Console's Datastore
Statistics, we now offer namespace suggest  for filtering stats.- We
have released as experimental the full MapReduce framework.- The
mail_stub.get_sent_messages() call now returns EmailMessage
instances.- Fixed an issue when setting an initial_value in
memcache.incr unexpectedly  returned a string.
http://code.google.com/p/googleappengine/issues/detail?id=2012
-
Fixed an issue where DoS stats in the Admin Console didn't work for
High  Replication apps.
http://code.google.com/p/googleappengine/issues/detail?id=5237


App Engine Java SDK - Release NotesVersion 1.6.0=- On
November 7th, App Engine will be out of Preview. The new Terms of
Service  and previously announced pricing changes will be in effect.
Additionally, all  paid apps are now covered by our SLA.
http://www.google.com/enterprise/cloud/appengine/pricing.html
-
Paid apps can now specify the maximum pending latency for instances
and the  minimum number of idle instances for your application in the
Admin Console.- We have released an experimental utility, available in
the Admin Console, to  assist in migrating your application to the
High Replication datastore. This  utility allows you to copy the bulk
of your data in the background, while the  source application is still
serving. You then need a brief read-only period to  migrate your
application data while you copy the data that has changed from  the
time the original copy started.- Blobstore, which was previously
limited to apps with billing enabled, is now  available for all apps.-
We have published a new article on Datastore Index Selection and
Advanced  Search which explains our recent improvements to the query
planner that make  exploding indexes unnecessary.
http://code.google.com/appengine/articles/indexselection.html
-
Applications can now receive xmpp error stanzas at /_ah/xmpp/error.-
In the Admin Console data viewer, you can now filter by namespace from
a drop  down menu, if applicable.- In the Admin Console's Datastore
Statistics, we now offer namespace suggest  for filtering stats.-
Added API functionality for making calls to the Memcache API
asynchronously.- In the Memcache API, getIdentifiable() and
putIfUntouched() now support  batch operations.- We've added a page,
/_ah/admin/capabilitiesstatus, to the dev console that  allows you to
configure the capability state o

Re: [google-appengine] Re: TemplateSyntaxError: Caught ImportError while rendering: No module named http (while migrating py2.5 to py2.7 application)

[Brian Quinlan]

Hi Mariano,

Thanks for bringing this up. I'll take a look at the issue some time
day and report back.

Cheers,
Brian

On Mon, Oct 31, 2011 at 11:26 PM, Mariano Benitez  wrote:
>
> looking at the sources here I found this line:
> from google.appengine._internal.django.http import Http404
> package http is not there in the sources, but I found that class Http404 is 
> now in django package itself here
>
>
> Any help is appreciated!!!
> Thanks,
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/google-appengine/-/ANIciPS8ikoJ.
> 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.

-- 
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: Critical bug with Python Queries with Equal filters

[Alex Popescu]

This was embarrassing... Please forgive and forget about this post.

-- 
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.

Re: [google-appengine] Early experimental release of Yaac! Which allows you execute query with aggregation functions / multiple inequality filters etc.

[Waleed Abdulla]

I really like this project and have been hoping someone would do it for a
long time. The need to run arbitrary reports on the datastore is clear, and
the current tools are a pain. So this is a great start. My feedback:

- It's still buggy. I ran a few queries and only some of them worked, and
the others just get stuck in processing.

- Definitely change the name. "Yet another..." makes it feel cheap.

- I don't like the concept of running it as a separate version. I prefer to
drop the code in a separate folder in my project and access it with it's
own path (e.g. /yaac), just like appstats and mapreduce.

- I would suggest focusing on EGQL and making it really solid. Remove the
other features (blobstore, memcache, taskqueues...etc) to avoid
distractions until EGQL is robust. Expanding the scope at this early stage
will only spread your efforts too thin and you end up with many half-baked
features that no one wants to use.

Good luck,
Waleed



On Mon, Oct 31, 2011 at 9:24 AM, Max  wrote:

> As we all know we can not use join, aggregation functions, group by or
> multiple inequalities in datastore query. Google's argument is these
> relational feature are not scalable. But there has to be some use cases
> like ad hoc request to generate some report. We then have to prepare / test
> our own mapreduce / pipeline scripts and deploy to production environment,
> which is usually error prone and not trivial.
>
> Project Yaac(Yet Another Admin Console) is targeted to solve this common
> use case. Yaac is not a standalone java or python library, instead it's a
> complete application which is designed to be deployed to your own domain
> (non-default version of course). Yaac provides Extended GQL(EGQL), which
> supports aggregation function / group by / complex nested expressions /
> multiple inequality filters / *not*, *or* clause in where condition. For
> instance, in a football datastore, you can execute following EGQL query:
>
>  select HOME_TEAM, AWAY_TEAM, COUNT(1), sum(FTHG > FTAG), sum(FTHG =
> FTAG), sum(FTHG < FTAG)
>  from MATCH
>  where HOME_TEAM = "Arsenal"
>  group by HOME_TEAM, AWAY_TEAM
>  having sum(FTHG > FTAG) > sum(FTHG = FTAG) + sum(FTHG < FTAG)
>
> More details visit this page:
> http://code.google.com/p/yaac/wiki/EGQLReference Because it's an early
> experimental verion, some part of the language may subject to change in the
> future.
>
> There is also a sandbox environment
> http://sandbox.yetanotheradminconsole.appspot.com/. Anyone with a Google
> account can login and play with Sandbox. Simply go to Datastore -->
> Extended GQL then execute above query. I have uploaded 86000 football
> matches (all matches played in 10 leagues for last 18 seasons). For
> example, to retrieve all matches played in Arsenal's home against Man
> United after year 2000 and at least one teams scored in the game. We can
> execute following query:
>
> select HOME_TEAM, AWAY_TEAM, format(MATCH_DATE, "MMM dd, "), FTHG,
> FTAG
> from MATCH
> where HOME_TEAM = "Arsenal" and AWAY_TEAM = "Man United" and MATCH_DATE >
> datetime("2101") and FTHG + FTAG > 0
>
> (FTHG means full time home goal :) )
>
> It only tooks several steps to deploy Yaac to your own domain, check out
> http://code.google.com/p/yaac/wiki/DeployGuideline
>
> Again, it's a very very early experimental release, you may notice that
> the performance is extremely slow. This is because all queries are executed
> by pipeline API in a niave way, sequential scanning over whole datastore. I
> will spend more time to optimize it these days.
>
> Please try to set batch size to a smaller value if you are not performing
> query with aggregation / group by, otherwise it's very easy for a result
> message to hit channel service single message size limit (32KB). This will
> also be fixed soon.
>
> I will also try to provide a better error / exception messages when there
> is an error in query syntax or during query execution
>
> Any comments? Feedbacks? Feature requests are all welcome!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/bwwGQ0MGjJ0J.
> 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.
>

-- 
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: How to set up task queues to prevent bursts?

[Dale]

What about using pull queues? Your external system could poll the
queues for work, and scale based on the number of items in the queue.
That would give you the most control. If you didn't want to poll, you
could set up a push notification to your external system, telling it
that there is new work available.

On Oct 31, 7:21 am, Pol  wrote:
> Good point, forcing the tasks to retry every few seconds instead of at
> an increasing back off might do it. Keep pounding the system to force
> it to scale, but it's not very elegant :)
>
> My original idea was to play with the "bucket size" parameter for the
> queue, as the docs seem to imply that it allows to control bursts, but
> it's not clear at all. I reduced it to 1, but I don't understand what
> it means in practice if max rate and max concurrency are at 200.
>
> On Oct 30, 10:13 pm, Jeff Schnitzer  wrote:
>
> > Interesting problem.  While the sudden load may be undesirable it seems
> > that the real problem is that the task queue backoff is too aggressive - if
> > it kept trying, it would eventually spin up enough hardware at the external
> > system.
>
> > You can configure the retry schedule explicitly - maybe try setting it so
> > that requests are retried more often?  You'll still get the initial errors
> > but at least you'll get the queues cleared eventually.
>
> > Jeff
>
> > On Sun, Oct 30, 2011 at 10:07 PM, Pol  wrote:
> > > Sorry, I realize I didn't explain everything: since the external
> > > system can handle an arbitrary load (as long as this load doesn't grow
> > > too fast) and requests get processed in 1 to 2 seconds, we already set
> > > the processing rate to the maximum (200), as well as the concurrent
> > > (200).
>
> > > The problem is not to limit the number of requests being handled, but
> > > preventing bursts e.g. scaling up smoothly.
>
> > > On Oct 30, 9:22 pm, Nicholas Verne  wrote:
> > > > If your external system is called synchronously by your tasks, you could
> > > > try setting the queue's max_concurrent_requests parameter in
> > > queue.yaml/xml
>
> > > > This is documented for Java, but the same general rules apply for Python
> > > or
> > > > Go applications.
> > >http://code.google.com/appengine/docs/java/config/queue.html#Defining...
>
> > > > Nick Verne
>
> > > > On Mon, Oct 31, 2011 at 3:13 PM, Pol  wrote:
> > > > > Hi,
>
> > > > > Through a task queue, we manage calls from GAE to an external system,
> > > > > which is fully-scalable but takes minutes to do so. The task queue
> > > > > rate is therefore set to 200/s.
>
> > > > > So what happens is that sometimes we get bursts of activity, and the
> > > > > task queue sends 200 requests at once: the vast majority fails in the
> > > > > external system as it can't handle this sudden request in load. But
> > > > > the external system doesn't start scaling up as there are no more
> > > > > requests coming and it's scaling based on the CPU load. Then suddenly
> > > > > you get another burst of requests from the task queue retrying, and
> > > > > then again the majority fails and so on.
>
> > > > > So how can we configure a task queue to have a very high rate *but*
> > > > > prevent it to get to this rate too fast? I noticed the bucket size
> > > > > parameter, but I'm not sure how to use it properly.
>
> > > > > Thanks,
>
> > > > > - Pol
>
> > > > > --
> > > > > 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.
>
> > > --
> > > 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.

-- 
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] Critical bug with Python Queries with Equal filters

[Alex Popescu]

Hi all,

I'm wondering if someone else have seen this before and has any ideas
what could lead to this completely confusing behavior


class Content(Model):
  uri = db.URLProperty(required=True)
  content_type = db.IntegerProperty(required=True, choices=[1, 2, 3,
4, 5,6,7,10, -1])
  title = db.StringProperty()

uri=u'http://basho.com/blog/technical/2011/09/19/Riak-Pipe-The-New-Map-
Reduce-Power'
results = Content.all().filter('uri = ', uri).fetch(5)
for c in results:
  print "'%s'" % c.uri

=> returns no results

while changing the filter to use greater than:

uri=u'http://basho.com/blog/technical/2011/09/19/Riak-Pipe-The-New-Map-
Reduce-Power'
results = Content.all().filter('uri >= ', uri).fetch(5)
for c in results:
  print "'%s'" % c.uri

=> returns:

'http://basho.com/blog/technical/2011/09/19/Riak-Pipe-The-New-Map-
Reduce-Power/'
'http://basho.com/blog/technical/2011/09/19/Riak-Pipe-The-New-Map-
Reduce-Power/'
'http://basho.com/blog/technical/2011/09/19/Riak-Pipe-The-New-Map-
Reduce-Power/'

I've been staring at this code for the last 30 minutes and I cannot
understand what's wrong with it, except maybe some broken internal
index.

Or am I missing something?

-- 
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.

Re: [google-appengine] Can I delete task and create it immediately by re-using the same task name?

[Brian Quinlan]

On Tue, Nov 1, 2011 at 3:35 AM, Andrius  wrote:

> Hello,
>
> Can I delete a task by running Queue.delete_tasks() based on unique
> task name and add a new task with the same name?
>
> Queue.delete_tasks(Task(name='myTask'))
> Queue.add(Task(name='myTask'...))
>
> Will that work? I know that previously this method was not available
> and you couldn't reuse the task names for some time..
>

No, task names are not reusable for around 7 days.

Cheers,
Brian


> Would be grateful for your knowledge!
>
> Thanks,
> Andrius
>
> --
> 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.
>
>

-- 
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: Is GAE still using old pricing scheme ?

[Philip]

Hey Greg,

how do we avoid over-quota errors if we cannot edit the budget for
instance hours?

On Oct 31, 7:16 pm, "Gregory D'alesandre"  wrote:
> Just a slight change, the new pricing will actually kick in on Nov 7th.  We
> are sending out an email to all admins or running applications about this
> tomorrow.  If you have any questions on this, please let me know!
>
> Greg D'Alesandre
> Senior Product Manager, Google App Engine
>
>
>
>
>
>
>
> On Mon, Oct 31, 2011 at 2:45 AM, Philip  wrote:
> > "me" must be misinformed :-)
> > The new pricing will kick in tomorrow.
>
> > On Oct 31, 9:20 am, Prashant  wrote:
> > > Hi,
>
> > > My GAE apps still show old quota limits. According to me new pricing and
> > > quota schemes should be applicable by now. If it is not, when it is going
> > > to be effective from ?
>
> > > --
> > > Prashant
>
> > --
> > 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.

-- 
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.

Re: [google-appengine] Re: Is GAE still using old pricing scheme ?

[Gregory D'alesandre]

Just a slight change, the new pricing will actually kick in on Nov 7th.  We
are sending out an email to all admins or running applications about this
tomorrow.  If you have any questions on this, please let me know!

Greg D'Alesandre
Senior Product Manager, Google App Engine

On Mon, Oct 31, 2011 at 2:45 AM, Philip  wrote:

> "me" must be misinformed :-)
> The new pricing will kick in tomorrow.
>
> On Oct 31, 9:20 am, Prashant  wrote:
> > Hi,
> >
> > My GAE apps still show old quota limits. According to me new pricing and
> > quota schemes should be applicable by now. If it is not, when it is going
> > to be effective from ?
> >
> > --
> > Prashant
>
> --
> 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.
>
>

-- 
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] Can I delete task and create it immediately by re-using the same task name?

[Andrius]

Hello,

Can I delete a task by running Queue.delete_tasks() based on unique
task name and add a new task with the same name?

Queue.delete_tasks(Task(name='myTask'))
Queue.add(Task(name='myTask'...))

Will that work? I know that previously this method was not available
and you couldn't reuse the task names for some time..

Would be grateful for your knowledge!

Thanks,
Andrius

-- 
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] Early experimental release of Yaac! Which allows you execute query with aggregation functions / multiple inequality filters etc.

[Max]

As we all know we can not use join, aggregation functions, group by or 
multiple inequalities in datastore query. Google's argument is these 
relational feature are not scalable. But there has to be some use cases 
like ad hoc request to generate some report. We then have to prepare / test 
our own mapreduce / pipeline scripts and deploy to production environment, 
which is usually error prone and not trivial.

Project Yaac(Yet Another Admin Console) is targeted to solve this common 
use case. Yaac is not a standalone java or python library, instead it's a 
complete application which is designed to be deployed to your own domain 
(non-default version of course). Yaac provides Extended GQL(EGQL), which 
supports aggregation function / group by / complex nested expressions / 
multiple inequality filters / *not*, *or* clause in where condition. For 
instance, in a football datastore, you can execute following EGQL query:

 select HOME_TEAM, AWAY_TEAM, COUNT(1), sum(FTHG > FTAG), sum(FTHG = FTAG), 
sum(FTHG < FTAG) 
 from MATCH 
 where HOME_TEAM = "Arsenal" 
 group by HOME_TEAM, AWAY_TEAM
 having sum(FTHG > FTAG) > sum(FTHG = FTAG) + sum(FTHG < FTAG) 

More details visit this page: 
http://code.google.com/p/yaac/wiki/EGQLReference Because it's an early 
experimental verion, some part of the language may subject to change in the 
future.

There is also a sandbox environment 
http://sandbox.yetanotheradminconsole.appspot.com/. Anyone with a Google 
account can login and play with Sandbox. Simply go to Datastore --> 
Extended GQL then execute above query. I have uploaded 86000 football 
matches (all matches played in 10 leagues for last 18 seasons). For 
example, to retrieve all matches played in Arsenal's home against Man 
United after year 2000 and at least one teams scored in the game. We can 
execute following query:

select HOME_TEAM, AWAY_TEAM, format(MATCH_DATE, "MMM dd, "), FTHG, FTAG 
from MATCH 
where HOME_TEAM = "Arsenal" and AWAY_TEAM = "Man United" and MATCH_DATE > 
datetime("2101") and FTHG + FTAG > 0

(FTHG means full time home goal :) )

It only tooks several steps to deploy Yaac to your own domain, check out 
http://code.google.com/p/yaac/wiki/DeployGuideline
 
Again, it's a very very early experimental release, you may notice that the 
performance is extremely slow. This is because all queries are executed by 
pipeline API in a niave way, sequential scanning over whole datastore. I 
will spend more time to optimize it these days.

Please try to set batch size to a smaller value if you are not performing 
query with aggregation / group by, otherwise it's very easy for a result 
message to hit channel service single message size limit (32KB). This will 
also be fixed soon.

I will also try to provide a better error / exception messages when there 
is an error in query syntax or during query execution

Any comments? Feedbacks? Feature requests are all welcome!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/bwwGQ0MGjJ0J.
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] How work mail recieve?

[rekby]

I see:
when I have exception in inbound email handler - GAE retry request. How 
many times or how long time request will be to retry?
What will be with email when retries stop: send mail delivery failure for 
sender or silent drop email?

What will be if my quota is end? (Inbound traffic, cpu etc)

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/l8RwS7tgvewJ.
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.

Re: [google-appengine] Re: wildcard host mappings to ghs.google.com

[Chris Copeland]

Not a registrar, but we use http://www.dnsmadeeasy.com/ for DNS hosting and
they support it.

-Chris

2011/10/29 Ronoaldo José de Lana Pereira 

> Hi,
>
> http://www.enom.com/ seems to support this.
>
> Hope this helps
>
> -Ronoaldo
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/zeTvNH-T4R4J.
>
> 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.
>

-- 
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.

Re: [google-appengine] Deploy drops data

[Barry Hunter]

Well I was just going to suggest you use the datasotre admin
http://code.google.com/appengine/docs/adminconsole/datastoreadmin.html

to view your datastore, to see if the data is still there.

On Mon, Oct 31, 2011 at 2:32 PM, Phil McDonnell
 wrote:
> Also, minor possibility, but I noticed "Datastore Admin" was enabled in my
> settings.  Perhaps there is a bug associated with that and deploys?
> Thanks,
> Phil
>
> On Mon, Oct 31, 2011 at 10:27 AM, Phil McDonnell
>  wrote:
>>
>> I investigated the namespace idea and I don't believe that's being used
>> here at all. The one data class that is still accessible is a remnant from
>> some earlier work and no longer used which may explain why it doesn't become
>> inaccessible/disappear.
>> Any more ideas on how entire datastore classes might become inaccessible
>> directly after a deploy?  It does not happen every time I deploy, but when
>> it does it makes all of our data inaccessible, with the exception of the one
>> data class that we don't use anymore.
>> Thanks for your help and input,
>> Phil
>>
>> On Fri, Oct 28, 2011 at 4:18 PM, Phil McDonnell
>>  wrote:
>>>
>>> Hi guys,
>>> Apologies for using unclear terminology on this.  I understand the
>>> details of how the data is stored on BT. This is not local - this is on the
>>> production instance.
>>> This idea of something happening that makes the data inaccessible sounds
>>> possible. I'm running on version 2 of my app.  Could that be an issue?  I'm
>>> not very familiar with the namespace feature, but I can read up on this.
>>>  Are there other ways that the data might disappear?
>>> Ikai, in case it's useful, my app id is coupflipsite.
>>> Thanks so much for all the thoughts here.  Getting to the bottom of this
>>> is extremely important for us and I very much appreciate your wisdom on
>>> this.
>>> Thanks again,
>>> Phil
>>> On Fri, Oct 28, 2011 at 2:18 PM, Ikai Lan (Google) 
>>> wrote:

 Thanks for the explanation Barry. Phil, it sounds like you are talking
 about the local datastore. Can you clarify?
 --
 Ikai Lan
 Developer Programs Engineer, Google App Engine
 plus.ikailan.com | twitter.com/ikai


 On Fri, Oct 28, 2011 at 3:29 AM, Barry Hunter 
 wrote:
>
> That doesn't even make sense
>
> The Datastore has no concept of 'table'.
>
> All Entities - regardless of their kind- are stored in one 'bigtable'
> - they are all intermingled. In fact all Entities from everyone's apps
> are stored in the same bigtable.
>
> So to delete a 'table' - which is really just all entities of a given
> kind for a given app - would need to loop though and delete each
> individual entity. Once there are no entities of a given kind/model
> left, the 'kind' has effectively been dropped.
>
>
> I would guess need to check you aren't somehow using the application
> version in the Kind name or even the key?. Then when the application
> is updated, the version changes and therefore the old entities become
> inaccessible.
>
>
>
>
>
> On Thu, Oct 27, 2011 at 10:17 PM, Phil McDonnell
>  wrote:
> > Twice now a deploy has cleared several of the data tables in my
> > deployed
> > datastore.  Does anyone know what causes this?  The symptoms both
> > times are
> > consistent.  I do a deploy and the datastore drops several of the
> > tables.
> >  Strangely, one very old (and generally unused) table is not dropped
> > and my
> > blob data is still there.  Is this dropping of data/tables  on deploy
> > a
> > known "feature" that I'm somehow not understanding?  Note, this does
> > not
> > happen on every deploy.
> > We are still pre-launch, but I'm extremely concerned that this could
> > happen
> > when we are live.  If we drop our data when we are live it would cost
> > us a
> > lot of money.
> > Thanks so much,
> > Phil
> >
> > --
> > 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.
> >
>
> --
> 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.
>

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

Re: [google-appengine] Deploy drops data

[Phil McDonnell]

Also, minor possibility, but I noticed "Datastore Admin" was enabled in my
settings.  Perhaps there is a bug associated with that and deploys?

Thanks,
Phil

On Mon, Oct 31, 2011 at 10:27 AM, Phil McDonnell  wrote:

> I investigated the namespace idea and I don't believe that's being used
> here at all. The one data class that is still accessible is a remnant from
> some earlier work and no longer used which may explain why it doesn't
> become inaccessible/disappear.
>
> Any more ideas on how entire datastore classes might become inaccessible
> directly after a deploy?  It does not happen every time I deploy, but when
> it does it makes all of our data inaccessible, with the exception of the
> one data class that we don't use anymore.
>
> Thanks for your help and input,
> Phil
>
>
> On Fri, Oct 28, 2011 at 4:18 PM, Phil McDonnell <
> phil.a.mcdonn...@gmail.com> wrote:
>
>> Hi guys,
>>
>> Apologies for using unclear terminology on this.  I understand the
>> details of how the data is stored on BT. This is not local - this is on the
>> production instance.
>>
>> This idea of something happening that makes the data inaccessible sounds
>> possible. I'm running on version 2 of my app.  Could that be an issue?  I'm
>> not very familiar with the namespace feature, but I can read up on this.
>>  Are there other ways that the data might disappear?
>>
>> Ikai, in case it's useful, my app id is coupflipsite.
>>
>> Thanks so much for all the thoughts here.  Getting to the bottom of this
>> is extremely important for us and I very much appreciate your wisdom on
>> this.
>>
>> Thanks again,
>> Phil
>>
>> On Fri, Oct 28, 2011 at 2:18 PM, Ikai Lan (Google) wrote:
>>
>>> Thanks for the explanation Barry. Phil, it sounds like you are talking
>>> about the local datastore. Can you clarify?
>>>
>>> --
>>> Ikai Lan
>>> Developer Programs Engineer, Google App Engine
>>> plus.ikailan.com | twitter.com/ikai
>>>
>>>
>>>
>>> On Fri, Oct 28, 2011 at 3:29 AM, Barry Hunter wrote:
>>>
 That doesn't even make sense

 The Datastore has no concept of 'table'.

 All Entities - regardless of their kind- are stored in one 'bigtable'
 - they are all intermingled. In fact all Entities from everyone's apps
 are stored in the same bigtable.

 So to delete a 'table' - which is really just all entities of a given
 kind for a given app - would need to loop though and delete each
 individual entity. Once there are no entities of a given kind/model
 left, the 'kind' has effectively been dropped.


 I would guess need to check you aren't somehow using the application
 version in the Kind name or even the key?. Then when the application
 is updated, the version changes and therefore the old entities become
 inaccessible.





 On Thu, Oct 27, 2011 at 10:17 PM, Phil McDonnell
  wrote:
 > Twice now a deploy has cleared several of the data tables in my
 deployed
 > datastore.  Does anyone know what causes this?  The symptoms both
 times are
 > consistent.  I do a deploy and the datastore drops several of the
 tables.
 >  Strangely, one very old (and generally unused) table is not dropped
 and my
 > blob data is still there.  Is this dropping of data/tables  on deploy
 a
 > known "feature" that I'm somehow not understanding?  Note, this does
 not
 > happen on every deploy.
 > We are still pre-launch, but I'm extremely concerned that this could
 happen
 > when we are live.  If we drop our data when we are live it would cost
 us a
 > lot of money.
 > Thanks so much,
 > Phil
 >
 > --
 > 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.
 >

 --
 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.


>>>  --
>>> 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.
>>>
>>
>>
>

-- 
You received this message because you are subscribed to the Go

Re: [google-appengine] Deploy drops data

[Phil McDonnell]

I investigated the namespace idea and I don't believe that's being used
here at all. The one data class that is still accessible is a remnant from
some earlier work and no longer used which may explain why it doesn't
become inaccessible/disappear.

Any more ideas on how entire datastore classes might become inaccessible
directly after a deploy?  It does not happen every time I deploy, but when
it does it makes all of our data inaccessible, with the exception of the
one data class that we don't use anymore.

Thanks for your help and input,
Phil

On Fri, Oct 28, 2011 at 4:18 PM, Phil McDonnell
wrote:

> Hi guys,
>
> Apologies for using unclear terminology on this.  I understand the details
> of how the data is stored on BT. This is not local - this is on the
> production instance.
>
> This idea of something happening that makes the data inaccessible sounds
> possible. I'm running on version 2 of my app.  Could that be an issue?  I'm
> not very familiar with the namespace feature, but I can read up on this.
>  Are there other ways that the data might disappear?
>
> Ikai, in case it's useful, my app id is coupflipsite.
>
> Thanks so much for all the thoughts here.  Getting to the bottom of this
> is extremely important for us and I very much appreciate your wisdom on
> this.
>
> Thanks again,
> Phil
>
> On Fri, Oct 28, 2011 at 2:18 PM, Ikai Lan (Google) wrote:
>
>> Thanks for the explanation Barry. Phil, it sounds like you are talking
>> about the local datastore. Can you clarify?
>>
>> --
>> Ikai Lan
>> Developer Programs Engineer, Google App Engine
>> plus.ikailan.com | twitter.com/ikai
>>
>>
>>
>> On Fri, Oct 28, 2011 at 3:29 AM, Barry Hunter wrote:
>>
>>> That doesn't even make sense
>>>
>>> The Datastore has no concept of 'table'.
>>>
>>> All Entities - regardless of their kind- are stored in one 'bigtable'
>>> - they are all intermingled. In fact all Entities from everyone's apps
>>> are stored in the same bigtable.
>>>
>>> So to delete a 'table' - which is really just all entities of a given
>>> kind for a given app - would need to loop though and delete each
>>> individual entity. Once there are no entities of a given kind/model
>>> left, the 'kind' has effectively been dropped.
>>>
>>>
>>> I would guess need to check you aren't somehow using the application
>>> version in the Kind name or even the key?. Then when the application
>>> is updated, the version changes and therefore the old entities become
>>> inaccessible.
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Oct 27, 2011 at 10:17 PM, Phil McDonnell
>>>  wrote:
>>> > Twice now a deploy has cleared several of the data tables in my
>>> deployed
>>> > datastore.  Does anyone know what causes this?  The symptoms both
>>> times are
>>> > consistent.  I do a deploy and the datastore drops several of the
>>> tables.
>>> >  Strangely, one very old (and generally unused) table is not dropped
>>> and my
>>> > blob data is still there.  Is this dropping of data/tables  on deploy a
>>> > known "feature" that I'm somehow not understanding?  Note, this does
>>> not
>>> > happen on every deploy.
>>> > We are still pre-launch, but I'm extremely concerned that this could
>>> happen
>>> > when we are live.  If we drop our data when we are live it would cost
>>> us a
>>> > lot of money.
>>> > Thanks so much,
>>> > Phil
>>> >
>>> > --
>>> > 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.
>>> >
>>>
>>> --
>>> 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.
>>>
>>>
>>  --
>> 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.
>>
>
>

-- 
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: TemplateSyntaxError: Caught ImportError while rendering: No module named http (while migrating py2.5 to py2.7 application)

[Mariano Benitez]

looking at the sources 
here
 I 
found this line: 

from google.appengine._internal.django.http import Http404
package http is not there in the sources, but I found that class Http404 is 
now in django package itself 
here


Any help is appreciated!!!

Thanks,

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/ANIciPS8ikoJ.
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] TemplateSyntaxError: Caught ImportError while rendering: No module named http (while migrating py2.5 to py2.7 application)

[Mariano Benitez]

I am porting my app to python 2.7 and I got it running until I try to 
render my templates. I cannot easily trace which tag or filter is causing 
trouble...

I get the following stack trace:

Caught ImportError while rendering: No module named http
Traceback (most recent call last):
  File 
"/base/python27_runtime/python27_lib/versions/third_party/webapp2-2.3/webapp2.py",
 line 1511, in __call__
rv = self.handle_exception(request, response, e)
  File 
"/base/python27_runtime/python27_lib/versions/third_party/webapp2-2.3/webapp2.py",
 line 1505, in __call__
rv = self.router.dispatch(request, response)
  File 
"/base/python27_runtime/python27_lib/versions/third_party/webapp2-2.3/webapp2.py",
 line 1253, in default_dispatcher
return route.handler_adapter(request, response)
  File 
"/base/python27_runtime/python27_lib/versions/third_party/webapp2-2.3/webapp2.py",
 line 1077, in __call__
return handler.dispatch()
  File 
"/base/python27_runtime/python27_lib/versions/third_party/webapp2-2.3/webapp2.py",
 line 547, in dispatch
return self.handle_exception(e, self.app.debug)
  File 
"/base/python27_runtime/python27_lib/versions/third_party/webapp2-2.3/webapp2.py",
 line 545, in dispatch
return method(*args, **kwargs)
  File 
"/base/data/home/apps/s~regalatufoto-v5/v44.354351615236544078/app/handlers/base.py",
 line 306, in get
self.processResponse(self.GetResponse())
  File 
"/base/data/home/apps/s~regalatufoto-v5/v44.354351615236544078/app/handlers/base.py",
 line 222, in smartGetResponse
response = self.buildResponse()
  File 
"/base/data/home/apps/s~regalatufoto-v5/v44.354351615236544078/app/handlers/base.py",
 line 344, in buildResponse
content = renderHtmlTemplate(templatePath, values)
  File 
"/base/data/home/apps/s~regalatufoto-v5/v44.354351615236544078/app/utils.py", 
line 115, in renderHtmlTemplate
return renderTemplate(path, values)
  File 
"/base/data/home/apps/s~regalatufoto-v5/v44.354351615236544078/app/utils.py", 
line 95, in renderTemplate
return template.render(fullpath, values, debug=True)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/ext/webapp/template.py",
 line 89, in render
return t.render(Context(template_dict))
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/ext/webapp/template.py",
 line 169, in wrap_render
return orig_render(context)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/__init__.py",
 line 173, in render
return self._render(context)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/__init__.py",
 line 167, in _render
return self.nodelist.render(context)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/__init__.py",
 line 794, in render
bits.append(self.render_node(node, context))
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/debug.py",
 line 72, in render_node
result = node.render(context)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/loader_tags.py",
 line 125, in render
return compiled_parent._render(context)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/__init__.py",
 line 167, in _render
return self.nodelist.render(context)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/__init__.py",
 line 794, in render
bits.append(self.render_node(node, context))
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/debug.py",
 line 72, in render_node
result = node.render(context)
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/template/defaulttags.py",
 line 361, in render
from google.appengine._internal.django.core.urlresolvers import reverse, 
NoReverseMatch
  File 
"/base/python27_runtime/python27_lib/versions/1/google/appengine/_internal/django/core/urlresolvers.py",
 line 12, in 
from google.appengine._internal.django.http import Http404
TemplateSyntaxError: Caught ImportError while rendering: No module named http


I included django 1.2 and PIL 1.1.7 in the libraries, but no difference...


Any help?

Thanks,

MAriano

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/CQE6cXubA1kJ.
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.

Re: [google-appengine] webapp2 Import Error

[Simon M]

Or you add webapp2 into the EXTRA_PATHS variable in the dev_appserver.py 
file.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/GBFpjrZCyRcJ.
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] Conversion API OCR

[Bruno Sandivilli]

Hi, i can't find any topic on OCR, in the Conversion API docs. It mesnions
the OCR feature, but dont give any example or reference. Thanks

-- 
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: Is GAE still using old pricing scheme ?

[Philip]

"me" must be misinformed :-)
The new pricing will kick in tomorrow.

On Oct 31, 9:20 am, Prashant  wrote:
> Hi,
>
> My GAE apps still show old quota limits. According to me new pricing and
> quota schemes should be applicable by now. If it is not, when it is going
> to be effective from ?
>
> --
> Prashant

-- 
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] Dashboard Moscow TimeZone

[rekby]

Now Moscow timezone have always UTC+4:00, but dashboard show time as +3:00.

Moscow timezone: http://en.wikipedia.org/wiki/Moscow#cite_note-RuTime-9

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/CtUPNQmu0q4J.
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.

Re: [google-appengine] Re: Announcing SSL for Custom Domains Trusted Tester Program

[Richard Watson]

Thanks, Jeff. Considering how much noise came of the pricing change, this 
should put some fire in bellies :)

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/UNBHi0JEIcQJ.
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] Is GAE still using old pricing scheme ?

[Prashant]

Hi,

My GAE apps still show old quota limits. According to me new pricing and
quota schemes should be applicable by now. If it is not, when it is going
to be effective from ?

--
Prashant

-- 
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.