Daniel Erat
Daniel Erat
@brainzbot, retest this please
@reosarevok and @yvanzo, I think this is ready for review now (when you have time). :-)
@mwiencek, would you mind taking a look at this one too? Thanks! @brainzbot, retest this please
@mwiencek, mind taking another look?
Thanks for all the help getting it merged!
I think I may have the opposite problem from what you're describing. My `/usr/bin/dev_appserver.py` (from `google-cloud-sdk-app-engine-python` `428.0.0-0`, which seems to be the latest version in the Apt repo) seems to...
Here's a disgusting hack that works around this by tricking `aetest` into using Python 3: ```go package main import ( "io/ioutil" "log" "os" "path/filepath" "google.golang.org/appengine/v2/aetest" ) func main() { dir,...
Is there any reason why `aetest` needs to explicitly choose a Python interpreter instead of just running `/usr/bin/dev_appserver.py` directly? That seems like it would do the right thing, at least...
For other users who run into this, an easier workaround to avoid the broken code is to just set `APPENGINE_DEV_APPSERVER_BINARY` beforehand: ```go os.Setenv("APPENGINE_DEV_APPSERVER_BINARY", "dev_appserver.py") inst, err := aetest.NewInstance(&aetest.Options{}) ```
I think that this is no longer an issue due to `dev_appserver.py` having been updated to use Python 3 (at 468, I believe).