4 ms·
I'm disappointed by this poor integration. I had hoped Google would at least make importing libraries somewhat easier by including them as official third party
by pdknsk 14y ago
I'm disappointed by this poor integration. I had hoped Google would at least make importing libraries somewhat easier by including them as official third party libraries.
http://developers.google.com/appengine/docs/python/tools/libraries27 http://developers.google.com/appengine/docs/python/tools/lib...
This is just marketing. For some actual added value, Google could've made the whole process of acquiring tokens and billing transparent. Click a button in the App Engine dashboard, and it gets new tokens from Twilio which are billed through Google.
- crabasa 14y agoDisclaimer: I work for Twilio This is more than just marketing, but less than what you're describing. A great deal of work went into updating and testing our helper libraries in the GAE environment, as well as building documentation and proof on concepts[1] for developers to learn from. Deeper forms of integration require heavier lifting and require buy-in across the organization. If partnerships like this are successful and improve the adoption and use of new tooling, I think it will be much easier to make a case for more integration down the line. [1]: http://twiliosandbox.appspot.com/ http://twiliosandbox.appspot.com/
- kevinburke 14y agoAgreed, although the community has started offering some fairly good solutions for integrating third party libraries into App Engine projects. This layout is pretty good, for example: http://stackoverflow.com/questions/4863557/how-do-i-manage-third-party-python-libraries-with-google-app-engine-virtualenv http://stackoverflow.com/questions/4863557/how-do-i-manage-t...