On new debian 8 installs using google_compute_engine virtualenv installed boto is broken

Not exactly sure what’s going on here but we are now seeing:

  File "/home/lex/local/lib/python2.7/site-packages/boto/__init__.py", line 1216, in <module>
    boto.plugin.load_plugins(config)
  File "/home/lex/local/lib/python2.7/site-packages/boto/plugin.py", line 93, in load_plugins
    _import_module(file)
  File "/home/lex/local/lib/python2.7/site-packages/boto/plugin.py", line 75, in _import_module
    return imp.load_module(name, file, filename, data)
  File "/usr/lib/python2.7/dist-packages/google_compute_engine/boto/boto_config.py", line 29, in <module>
    from google_compute_engine import config_manager
ImportError: No module named google_compute_engine

Note that this is a virtualenv installed copy of boto which ends up failing with an error in google_compute_engines vendoring(?) of boto?

[domenkozar]

Been hitting this (on travis-ci 14.04). Seems like google-compute-engine has a cyclic dependency on boto.

Global system-wide side effects are bad (lead into such trouble), this should be fixed at design level.

[illfelder]

We now have a PyPI package for the Linux guest environment.

The package is available using: pip install google-compute-engine.