There is no 1MB limit as such.

set(xrange(198000)) => Memory Error

h = set(xrange(100000))
set(xrange(114000)) => Memory Error # This time we managed more entries but in two sets?

h = set([(chr(x) * 250000) for x in xrange(256)])
=> NO MemoryError.

So how comes that one cannot have a set with 200K integer entries, but one can have a set with 256 strings totaling at around 61MB size?

Andreas

The local SDK doesn’t have any of the quota limits in place — at least I haven’t run into any.

It’s true that that needs to be addressed.

On the other hand, however, it will be good to be able to override those so that you can do things like restore backups locally without the same restrictions (so you can do things quicker without redirects, etc.) Then again, maybe having things always consistent is more important.

Sure there are issues, it’s a new technology and that’s to be expected. There’s also a lot that is great about it. It’s the best dev environment/language/framework I’ve used. It’s a joy to develop with Python and Django and to be able to deploy so easily.

So there are definitely a lot of positives.

And the most important thing is that I know have some of the best minds in the industry working to my app better — I’m talking about the Google engineers working on the Google App Engine team :) So I’m investing in the future of Google App Engine and I believe that it was the right decision to make.

We’re having teething problems at the moment but we’re overcoming them.

Limits are not a bad thing in and of themselves as long as they are known and you can avoid them and architect things accordingly.

The beauty of App Engine is that if you can get your app working well for one person, that’s the experience any number of people will have with it.

I like that :)