hi all! i've ported the venerable, old school server side shell app shell-hrd.appspot.com from Python 2 to 3: shell-py3.appspot.com. it's a full fledged, interactive Python REPL that runs its code server side inside the Python 3 Standard Environment. feel free to try it out!
in the process of porting a few nontrivial apps to Python 3, i regularly found myself asking how bits of the production runtime behaved. which directory on the filesystem is the virtualenv installed in? what do the app-default credentials look like, specifically? what are the WSGI (etc) environment variables set to? one way to answer these is to add logging that prints them, deploy that code, run it, make a request, and look at the logs. that iteration cycle is pretty slow, though. using this shell is way faster. it also includes a number of the new Google Cloud API libraries, including google.cloud.ndb, .logging, and .error_reporting, which has been useful for experimenting with them. feedback is welcome! -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/d2152351-0153-446e-980c-327181069bd5%40googlegroups.com.
