ERROR: (gcloud.preview.app.deploy) Answer error: [400] Invalid character in the file name: flask / ext / setuptools / script (dev) .tmpl

Question

I am trying to run an application in an application using the following command.

gcloud --project=xxx preview app deploy app.yaml 

Then I get the following error message

 Updating module [default]...| Updating module [default].../ Updating module [default]...failed. ERROR: (gcloud.preview.app.deploy) Error Response: [400] Invalid character in filename: server/lib/flask/ext/setuptools/script (dev).tmpl Build step 'Execute shell' marked build as failure Finished: FAILURE 

Content Script (dev) .tmpl

 # EASY-INSTALL-DEV-SCRIPT: %(spec)r,%(script_name)r __requires__ = %(spec)r __import__('pkg_resources').require(%(spec)r) __file__ = %(dev_path)r exec(compile(open(__file__).read(), __file__, 'exec')) 

Questions

• What is Script (dev) .tmpl
• Why am I getting this error.

---

updated based on first answer

I added the following to the app.yaml file.

skip_files: - server / lib / flask / ext / setuptools / script (dev) .tmpl

However, he still gives me the same error.

Answer 1

That way skip_files works, you have to hide special characters. Add this to your app.yaml

 skip_files: - server/lib/flask/ext/setuptools/script\ \(dev\).tmpl 

set your relative path according to your .yaml

Answer 2

• script (dev).tmpl is a Flask- related file. It is not very important for you to worry as a Flask user.

• This error is due to a bug in gcloud. The next release of gcloud (92.0.0) will fix it. At the same time, you can get around adding this file to the skip_files section in app.yaml .

Answer 3

I know this happened a few months later, but I just created a Google App Engine account and downloaded the SDK last week. I am using the latest Flask skeleton for GAE applications and I was getting the same error regarding script (dev).tmpl . (The file is located only in a different directory.)

I tried to use skip_file , and that didn't work either. I looked through the file skipping documentation, and I don't think that meant what we were trying to use it for. I deleted it and my little Hello World test deployed without further errors. I hope that when I build something more complex, I will not encounter errors ...