Okaara 1.0.36 is incompatible with the Python 2.7.12 Runtime

[bmbouter]

In between Okaara 1.0.35 and 1.0.36 changes were introduced that cause tracebacks when running Okaara 1.0.36 with Python 2.7.12. When using this with Pulp I get:

Traceback (most recent call last):
  File "/bin/pulp-admin", line 9, in <module> 
    load_entry_point('pulp-client-admin', 'console_scripts', 'pulp-admin')()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 547, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2720, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2380, in load
    return self.resolve()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2386, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0) 
  File "/home/vagrant/devel/pulp/client_admin/pulp/client/admin/__init__.py", line 3, in <module> 
    from pulp.client import launcher 
  File "/home/vagrant/devel/pulp/client_lib/pulp/client/launcher.py", line 15, in <module> 
    from okaara.prompt import COLOR_CYAN, COLOR_LIGHT_CYAN
  File "build/bdist.linux-x86_64/egg/okaara/prompt.py", line 16, in <module> 
ImportError: No module named builtins

When I downgrade back to Okaara 1.0.35 I do not receive the traceback and things work as expected. I have two questions:

1. Was the dropping of the Python 2.7.12 intentional?
2. Can support for the Python 2.6+ runtime be brought back please?

[jdob]

Crud, no, dropping it wasn't intentional :)

I'll take a look as soon as I can.

[werwty]

@jdob, #15 should fix this.

[jdob]

This should be fixed and has been released as 1.0.37