Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix entry point to point to new run_gui function #118

Merged
merged 1 commit into from
Oct 31, 2017

Conversation

llimeht
Copy link
Contributor

@llimeht llimeht commented Oct 31, 2017

The current entry point defined by setup.py has not caught up with the change to the function name for the entry point:

$ sasview
Traceback (most recent call last):
  File "/usr/bin/sasview", line 11, in <module>
    load_entry_point('sasview==4.2.0', 'console_scripts', 'sasview')()
  File "…/lib/python2.7/site-packages/pkg_resources/__init__.py", line 564, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File …/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2662, in load_entry_point
    return ep.load()
  File …/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2316, in load
    return self.resolve()
  File "…/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2326, in resolve
    raise ImportError(str(exc))
ImportError: 'module' object has no attribute 'run'

with the egg containing in sasview-4.2.0.egg-info/entry_points.txt:

[console_scripts]
sasview = sas.sasview.sasview:run

This patch replaces run with run_gui in the entry point.

@pkienzle pkienzle merged commit eabdddf into SasView:master Oct 31, 2017
@llimeht llimeht deleted the tmp/entry-point branch November 1, 2017 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants