Eclipse and Google App Engine: ImportError: No module named _sysconfigdata_nd; unrecognized arguments: –high_replication
Question:
Just upgraded to Ubuntu 13.04 and Eclipse complained with the following 2 errors:
1. ImportError: No module named _sysconfigdata_nd
ERROR 2013-03-25 07:26:43,559 http_runtime.py:221] unexpected port response from runtime ['']; exiting the development server
ERROR 2013-03-25 07:26:43,561 server.py:576] Request to '/_ah/warmup' failed
2. dev_appserver.py: error: unrecognized arguments: --high_replication
I’ve never encountered the first one. And for the second, I used to run google app engine applications by setting the --high_replication argument and it worked well. Why all the sudden, these two didn’t work? Thanks in advance.
Answers:
The “No module named _sysconfigdata_nd” is a bug in the Ubuntu package.
You can create a softlink as a workaround:
sudo ln -s /usr/lib/python2.7/plat-*/_sysconfigdata_nd.py /usr/lib/python2.7/
Depending on different conditions, updating virtualenv may actually be a better idea instead of this walkaround, as mentioned on linked bug reports. To update virtualenv you could use the following command:
sudo pip install --upgrade virtualenv
Just upgraded to Ubuntu 13.04 and Eclipse complained with the following 2 errors:
1. ImportError: No module named _sysconfigdata_nd
ERROR 2013-03-25 07:26:43,559 http_runtime.py:221] unexpected port response from runtime ['']; exiting the development server
ERROR 2013-03-25 07:26:43,561 server.py:576] Request to '/_ah/warmup' failed
2. dev_appserver.py: error: unrecognized arguments: --high_replication
I’ve never encountered the first one. And for the second, I used to run google app engine applications by setting the --high_replication argument and it worked well. Why all the sudden, these two didn’t work? Thanks in advance.
The “No module named _sysconfigdata_nd” is a bug in the Ubuntu package.
You can create a softlink as a workaround:
sudo ln -s /usr/lib/python2.7/plat-*/_sysconfigdata_nd.py /usr/lib/python2.7/
Depending on different conditions, updating virtualenv may actually be a better idea instead of this walkaround, as mentioned on linked bug reports. To update virtualenv you could use the following command:
sudo pip install --upgrade virtualenv