appcfg.py doesn't work. The parameters in command line are always neglected

1
votes

Several days ago I uploaded my first sample project to Google App Engine. Now I want to update it using command "appcfg.py -A my-first-gae-project-1119 update app.yaml", however, it keeps showing the menu of appcfg.py instead of updating the project. It seems no matter what I type after "appcfg.py", it will always be neglected them just as I only typed "appcfg.py".

Can anyone help fix this?

Thanks!

I just found this guy had the same problem with me: Google App Engine appcfg.py shows the help message for every command

But it seems he doesn't fix that...

By the way, I tried both python 2.7.8 and 2.7.10. If I use version lower than 2.7.8, then there will be an encoding error when I run "appcfg.py".

2
pythongoogle-app-engine
Is there an error message in the output, such as "error: Unknown action: '...'" or anything like that? Is the first line "Usage: appcfg.py [options] <action>", or something else? (The command looks good. I tried the same arguments and argument order and it worked for me.) – Dan Sanderson
There is no any error messages. The first line is just "Usage: ...". – Phoenix416
Hm. Which operating system are you using? Did you use the GAE SDK installer for that OS, or the .zip file? Does "appcfg.py help" print "... appcfg.py: error: Expected a single action argument." or something else? – Dan Sanderson
I am using Windows, and I'm sure I installed the right version... When I type "appcfg.py help", it still list the "Usage: ...". Actually, as long as I type "appcfg.py", then no matter what I append to it, it will only print the usage list. – Phoenix416
Just to clarify, "appcfg.py help" prints "Usage: appcfg.py help <action> ... appcfg.py: error: Expected a single action argument." followed by the list of possible actions, but no command line args. But it sounds like none of the args are making it to appcfg.py... – Dan Sanderson

2 Answers

0
votes

This is actually an issue affecting passing command line arguments to Python scripts in general on Windows, and is caused by a broken file association in the registry for *.py files. Most of the time this can be fixed by uninstalling Python and then re-installing (as an administrator) using the latest Python 2.7 installer.

For manual steps in fixing the registry entry there is an older question on StackOverflow with the solution.

0
votes
$ appcfg.py update main/app.yaml service1/app.yaml service2/app.yaml