On Tue, Dec 6, 2011 at 8:56 PM, Brian Quinlan <bquin...@google.com> wrote: > > There is a known bug where the combination of Python 2.7 and enabling > concurrent requests causes large latency increases. The Python 2.7 > runtime is still experimental and bugs like this are expected. >
Ok, I understand that. Greg, could you please let us know why we have the new full-sized instance hour for python and still not have python concurrent requests ? I'm asking because you wrote<http://groups.google.com/group/google-appengine/browse_thread/thread/a1bfa432e0c002a7/739169f799d8e69a> : Q: Will there be a solution for Python concurrency? Will this require any code changes? Python concurrency will be handled by our release of Python 2.7 on App Engine. We’ve heard a lot of feedback from our Python users who are worried that the incentive is to move to Java because of its support for concurrent requests, so we’ve made a change to the new pricing to account for that. *While Python 2.7 support is currently in progress it is not yet done *so we will be ** providing a half-sized instance for Python (at half the price) until Python 2.7 is released.* * Ok, I know. It was already released (as experimental), but I thought that the purpose to holding "full-sized instances" was to give to python users the concurrent requests. 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.
