Welcome to the Google App Engine Python runtime forum.

Before posting you may want to read our user maintained App Engine
Community FAQ: http://knol.google.com/k/marce/app-engine-community-faqs/vkzeph4si12v/1#.
These are questions written and maintained by the group's members. If
you get a great answer to your question, consider adding it to the
FAQ!

* Submitting Questions *

We love to answer your questions, and there are somethings you can do
to improve the response time and completeness.  Search the group to
see if anyone has posted a similar issue.  Include information on the
expected behavior and what you are seeing instead, stack traces are
always great, and so is the code that produces them.  It can also be
helpful to see if you can find the minimal amount of code that
reproduces the issue, so we can pinpoint the issue faster.

* The Issue Tracker *
With App Engine, you can file feature requests and issues in our issue
tracker: http://code.google.com/p/googleappengine/issues/list

Before submitting an issue, search to see if it already exists. If so,
star the issue, and add any more relevant information you might have.
Please don't add +1 to the issue, as every time a comment is added, it
emails the people who have starred the issue.

Once the issue is filed, we will triage the issue.  We categorize all
of our issues as either 'Features' or 'Defects'.

A feature indicates that it is working as we expect it to, and the
request is asking for an enhancement or modification to the current
behavior. Once we have read a feature we will change the status from
'New' to 'Acknowledged', indicating that we have read this request.
This does not indicate that the feature is being, or will ever be,
implemented.  If it is clear a feature will never be implemented, we
will mark it as 'WontFix'.  Once a feature is implemented, it will be
marked as 'Fixed'.

A defect is when a feature of App Engine doesn't behave in the
documented or expected fashion. Once we confirm the defect, we will
change the status from 'New' to 'Accepted'.  You can propose a fix for
the issue by following the guidelines listed here:
http://groups.google.com/group/google-appengine/web/how-to-submit-a-p...

Once the fix is live in both App Engine and the SDK we will mark the
issue as 'Fixed'.  Any known work arounds or need for clarification
will be posted by directly in the issue.

We do not currently set the 'priority' field in the App Engine issue
tracker.  Also, on some features and defects we may include the
'Component' to which the issue belongs.

* Ways to Contribute *

App Engine Cookbook - If you have a creative solution to a common
problem, why not share it with all of us? You can submit recipes with
code snippets at http://appengine-cookbook.appspot.com/ . Discuss and
vote on recipes which you find helpful or suggest improvements. The
cookbook is a great resource for finding ways to handle common design
challenges.

App Engine Open Source Projects Page - If you are working on an Open
Source App Engine project, or you are looking to contribute to one,
checkout our Open Source projects page:
http://groups.google.com/group/google-appengine/web/google-app-engine...

App Gallery - After you have developed your killer App Engine app,
submit it to our App Gallery: http://appgallery.appspot.com/

Articles - We've already published a couple of user submitted articles
at http://code.google.com/appengine/articles/. If you have written, or
want to write, a how-to article for App Engine, please email the group
owners for more information.  All articles must be published under the
Creative Commons license.

Patches - If you have a fix for a problem in the SDK you can always
submit a patch by following the directions here:
http://groups.google.com/group/google-appengine/web/how-to-submit-a-p...

Happy posting,

The App Engine Team