Hi, > ... and I agree with you. But the approach we are taking towards the Python > 2.7 runtime is something that could theoretically be genericized for other > runtimes.
That sounds interesting and I guess at a certain point it makes sense to have a generic runtime rather than implementing a new runtime each time. > There are different levels of engagement with external developers we can > have if there is enough interest. For instance, if a very solid group of > developers was passionate about bringing a PHP runtime to App Engine and > demonstrated: > a. A willingness to roll up their sleeves and slug through some of the hard > work > b. The project was more than a throwaway project. That is - there is long > term viability. > ... we'd look at some of the various ways we could lower the communication > barrier between their team and ours. Given our lack of PHP interpreter > experience on our team, this would, for all practical purposes, be the only > way for a real PHP runtime to exist on App Engine. We probably wouldn't > maintain it, but we'd work closely with the folks that do. What about other language support (Mono/.Net languages are mentioned), if there is an interest in the community at large - is this a key metric that is used to look at language support? Personally I'd like to help out with the python runtime, but my impression is that there is an extremely high barrier to entry (probably rightly so) to getting involved here (compared with other open source projects). Thanks for the responses - interesting to hear what's coming (and soon I can upgrade to python2.7) Kev -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. 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.
