[google-appengine] Re: Loading custom libraries with appengine_config.py

Hi Frank, The VM runtime doesn't automatically load appengine_config like the non-VM runtime. Here's two things you can do to use third-party packages: - Import appengine_config at the top of main.py - Take advantage of the Docker container and install everything via pip in your Dockerf

Re: [google-appengine] New App Engine Managed VM Docs

> > Are there plans to port over NDB for datastore access on managed VMs? > There is on-going discussion about NDB for Cloud Datastore here . The tl;dr is that basically it's possible, it's planned, but its

Re: [google-appengine] New App Engine Managed VM Docs

happy to review and merge your patch as well as publish a new version of webapp2 to PyPI. This process takes some time, so I will update this list once that is done. On Mon, Feb 22, 2016 at 1:01 PM Karl MacMillan wrote: > On Feb 22, 2016, at 3:44 PM, 'Jon Parrott' via Google App

Re: [google-appengine] New App Engine Managed VM Docs

(it's a third-party package). If we do gain ownership of it, we will likely put it into a community-supported model. On Mon, Feb 22, 2016 at 1:32 PM Karl MacMillan wrote: > On Feb 22, 2016, at 4:14 PM, 'Jon Parrott' via Google App Engine < > google-appengine@googlegrou

[google-appengine] Re: Managed VMs - Scipy

Hi Ludovic, Using SciPy on MVMs is absolutely possible. You have a few options: 1. You can try using the new Managed VMs Python Runtime , which should allow you to just add scipy to your requirements.txt (please le

Re: [google-appengine] Re: Managed VMs - Scipy

n.app > script: main.app > > *requirements.txt* > Flask==0.10.1 > Scipy==0.17.0 > > > And the message pasted in the original message is the error message I am > getting. > > Ludo > > > On Tuesday, February 23, 2016 at 4:26:13 PM UTC-8, Jon Parrott wrote:

Re: [google-appengine] Re: New App Engine Managed VM Docs

You don't actually need to create a new project to use Managed VMs. You can deploy to a new version or module within an existing application. Though we do highly recommend testing and monitoring your application before serving public traffic. On Wed, Mar 2, 2016 at 11:59 AM Adam Sah wrote: > hi

Re: [google-appengine] New App Engine Managed VM Docs

es -- but, ones based on almost 20 years' >> experience with Python (starting with a personal website project using CGI) >> and on being a Fellow of the PSF and a winner of the Frank Willison >> Memorial Award for contributions to Python:-). >> >> >> Alex

[google-appengine] Re: Painful Python GAE (managed VM), Protobuf interaction

We can make the SDK's google package a namespace package relatively easily. On Friday, March 4, 2016 at 6:21:36 PM UTC-8, Adrian Wan wrote: > > I'd like to call attention to this protobuf bug > , which has an > interaction with GAE. > > A brief su

[google-appengine] Re: Managed VM old docs anywhere ?

We'd love to hear feedback on how we can make the extending runtime and building custom runtime pages better as well. On Thursday, March 10, 2016 at 1:15:59 AM UTC-8, Su-Au Hwang wrote: > > Thanks for the link! > I've seen Appstart before and it looks like a great solution, albeit not > official

[google-appengine] Re: python managed VMs success story! (so far...)

Hey Adam, thanks for the great feedback. Can you give me a bit more details on PIL not working for you? Which runtime are you using? On Tuesday, March 8, 2016 at 8:14:14 PM UTC-8, Adam Sah wrote: > > quick followup and a good example of how it's easy to run components > side-by-side: > - Image

[google-appengine] Re: another wrinkle with GAE/Python Managed VMs: timezone set to local deploy location, not UTC like in GAE

To further Nick's point here, Python provides datetime.datetime.utcnow() which allows you to explicitly get the current time in UTC. It's almost always preferable to use that unless you explicitly want to deal with system-local time. On Wednesday, March 16, 2016 at 12:30:33 PM UTC-7, Nick (Clou

[google-appengine] hi i have a working website in python web2py that run in Google App Engine Standard Environment i want to pass the site to Google App Engine VM

Hi, can you give us more details? Are you getting any error messages? What step are you stuck on? -- 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-ap

Re: [google-appengine] Re: hi i have a working website in python web2py that run in Google App Engine Standard Environment i want to pass the site to Google App Engine VM

?.*/RCS/.*$ >> - ^(.*/)?\..*$ >> - Crypto >> >> *the model that i Importing the python script* >> >> import os >> import cgi >> import config >> import datetime >> import time >> import ee >> import jinja2 >> import webapp2 >&

[google-appengine] An update on webapp2

In a previous thread , several of you pointed out that webapp2 was abandoned and some of you expressed interesting in helping maintain the project. I'm happy to provide an update. The original author has allowed the Google C

Re: [google-appengine] New App Engine Managed VM Docs

te: > >> >> On Mar 4, 2016, at 1:57 PM, 'Jon Parrott' via Google App Engine < >> google-a...@googlegroups.com > wrote: >> >> Just a quick update on the webapp2 situation. The original author has >> graciously allowed us to take ownership. My team

Re: [google-appengine] An update on webapp2

> On Apr 8, 2016, at 4:58 PM, 'Jon Parrott' via Google App Engine < > google-a...@googlegroups.com > wrote: > > In a previous thread > <https://groups.google.com/forum/#!topic/google-appengine/HazEmXZRpiw>, > several of you pointed out that webapp2 was

[google-appengine] Re: App Engine internal implementations

Much of the public details of our underlying technology can be found as google research publications. Notably, things in the Distributed Systems and Parallel Computing section. Of particular note are the borg, bigtabl

Re: [google-appengine] An update on webapp2

+Max Sills Karl, our open-source team has indicated that because we now own the fork we need CLAs present. I've included Max from our open-source team who can follow up with the other concerns. On Mon, Apr 11, 2016 at 11:52 AM Karl MacMillan wrote: > On Apr 11, 2016, at 1:28 AM, 

[google-appengine] Re: ImportError: No module named webapp2

Can you provide us with a simple reproducible case? a github repo or gist would be easiest. On Wednesday, May 18, 2016 at 1:33:13 PM UTC-7, Anand Atreya wrote: > > It looks like the protobuf pip package conflicts with webapp2. I > temporarily resolved the issue by uninstalling all google python

Re: [google-appengine] Re: ImportError: No module named webapp2

Thanks for chiming in, Stephen. If you can provide a simple case where you can reproduce this, that would be really helpful in us figuring out why this is occurring. On Wed, May 25, 2016 at 9:45 AM Stephen Cagle wrote: > I just want to second that I also had a conflict with > googleapis-common-p

Re: [google-appengine] Re: ImportError: No module named webapp2

Thanks everyone for reporting this. We've reproduced the issue and and fix is incoming. It won't be in the next SDK release (38), but likely will be in 39 or 40. On Thursday, May 26, 2016 at 7:38:03 AM UTC-7, Matthieu Rouget wrote: > > Hello all, > > Same issue for me. > > I use the dev_appserve

Re: [google-appengine] Re: ImportError: No module named webapp2

I do not think so. On Wed, Jun 1, 2016 at 11:47 AM Michael Nadel wrote: > Thanks Jon. Is there an issue for this on http://code.google.com? > > > On Thursday, May 26, 2016 at 12:17:29 PM UTC-5, Jon Parrott wrote: >> >> Thanks everyone for reporting this. We've

[google-appengine] Re: Stackdriver Debugger for flexible environment

This is a known issue and we're working on fixing it. On Thursday, June 9, 2016 at 9:33:31 AM UTC-7, Amaury Gauthier wrote: > > Hello, > > On this page > we > can read: > >> Stackdriver Debugger is enabled automatically fo

[google-appengine] Re: Does Google App Engine (Flexible) Support Google Endpoints?

Robert and everyone: we hear you. Please keep in mind that App Engine Flexible is still in beta, and the Python compat runtime itself is in alpha. We're still doing a lot of work on both and we're still collecting user feedback. Things like this mailing list and the public issue track are some

Re: [google-appengine] Re: ImportError: No module named webapp2

The fix for this will be in the next App Engine SDK release (1.9.40). In the meantime, please use the workaround posted. On Friday, July 15, 2016 at 2:12:34 PM UTC-7, Huang-Wei Chang wrote: > > I am wondering is there any update? I tried version 38 and it indeed > doesn't work. It's really frust