Python snaps

Barry Warsaw barry at
Fri Apr 3 19:11:45 UTC 2015

On Apr 03, 2015, at 01:57 PM, Dustin Kirkland wrote:

>I didn't, but I do now, and the error was the same:

I get a different error:

Traceback (most recent call last):
  File "./", line 229, in _entry_point
    return super()._entry_point(config)
  File "./", line 76, in _entry_point
    return config['project']['entry_point']
  File "/usr/lib/python3.4/", line 1203, in __getitem__
    raise KeyError(key)
KeyError: 'entry_point'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "./", line 288, in <module>
  File "./", line 281, in main
    package.make_pex(config, dirs.bin)
  File "./", line 112, in make_pex
    subprocess.check_call(self._pexcmd(config, binary), shell=True)
  File "./", line 238, in _pexcmd
    ep = self._entry_point(config)
  File "./", line 234, in _entry_point
    assert len(eps['console_scripts']) == 1, eps['console_scripts']
  File "/usr/lib/python3.4/", line 937, in __getitem__
    raise KeyError(key)
KeyError: 'console_scripts'

Then I ran `python3 egg_info` on your git repo and noticed that
there's no ssh_import_id.egg-info/entry_points.txt file.  Indeed, looking at
your there are no console entry points defined. doesn't currently handle the `scripts` tag in  I'm not sure
pex itself handles that either because of the way it wraps invocation of your
entry points.

If you *can* define an entry point for the app you want to deploy, just add it
to your ini file, e.g.:

name: ssh-import-id
origin: git
entry_point: mypackage.mymodule:mainfunc

(this is passed directly to pex's -e argument)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the snappy-devel mailing list