thanks for the link, amit! that issue definitely looks related. this problem still happens for me on cloud SDK 220 + app-engine-python 1.9.77, so i may be seeing a different variation of that issue, since most people there say 220 fixed it for them. i've added a comment.
On Thursday, October 11, 2018 at 9:31:52 AM UTC-7, Amit (Google Cloud Support) wrote: > > Hello Ryan > > What is the current Google Cloud SDK version you are using? As of now current > version <https://cloud.google.com/sdk/docs/release-notes> for Google > Cloud SDK is [220.0.0]. We had a known issue [1] on version [219.0.1] in > dev_appserver with app-engine-python [1.9.76] which should be resolved in > the current version where the version of app-engine-python is [1.9.77]. I > would recommend to update your SDK version using this [2] command and try > again. If you still having this issue after upgrade and believe this could > be a bug, please create an issue in issuetracker > <https://cloud.google.com/support/docs/issue-trackers> with details > description of your issue and provide the output of this [3] command so > that we know more about your SDK. > > [1] https://issuetracker.google.com/117145272 > > [2] gcloud components update > > [3] gcloud info --anonymize > > > On Wednesday, October 10, 2018 at 6:51:57 PM UTC-4, Ryan B wrote: >> >> fwiw, i've deployed at least one of the affected apps since >> app-engine-python 1.9.76 was released, and it's still working fine, which >> implies that the prod runtime isn't similarly affected. (i did that deploy >> with gcloud sdk 218, purely out of superstition, but i didn't really expect >> it to matter much one way or the other.) >> >> On Wednesday, October 10, 2018 at 3:50:02 PM UTC-7, Ryan B wrote: >>> >>> hi all! i'm debugging a dev_appserver problem that seems to have been >>> introduced in google cloud sdk 219 / app-engine-python 1.9.76: imports are >>> now all resolved as absolute instead of relative. does that sound familiar? >>> >>> for example, i use the future library <http://python-future.org/> in >>> many of my apps, which has this line of code >>> <https://github.com/PythonCharmers/python-future/blob/fdd5eebe3aea61959533dbb722820fac7c5954ea/src/future/standard_library/__init__.py#L484> >>> : >>> >>> import test >>> >>> on gcloud sdk 218 / app-engine-python 1.9.75 and before, this worked >>> fine. it resolved the import relative to the containing source file, in >>> local/lib/python2.7/site-packages/future/... , a virtualenv, which i >>> set up with vendor >>> <https://cloud.google.com/appengine/docs/standard/python/tools/using-libraries-python-27#vendoring>. >>> >>> on 1.9.76, it changed to resolving absolute instead, so it imports an >>> unrelated test/ package directory in the top level of my app, which >>> obviously won't work, and the app breaks. >>> >>> i couldn't find any mention of this in release notes or docs. was this >>> expected? any recommendations for handling it? thanks in advance! >>> >>> >>> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/043b9c9d-f2f4-4aec-91bb-e94dc9d090d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
