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

ViTables fails to detect PyQt5 #78

Closed
cyanate opened this issue Aug 15, 2017 · 2 comments
Closed

ViTables fails to detect PyQt5 #78

cyanate opened this issue Aug 15, 2017 · 2 comments

Comments

@cyanate
Copy link

cyanate commented Aug 15, 2017

I'm using Arch and have python-qtpy and python-pyqt5 (v 5.9) installed, but ViTables anyway doesn't detect it:

  File "/usr/bin/vitables", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3049, in <module>
    @_call_aside
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3033, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3062, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 658, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 972, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 858, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'PyQt5>=5.5.1' distribution was not found and is required by ViTables
@uvemas
Copy link
Owner

uvemas commented Aug 15, 2017

Can you provide some more information please? In particular, how is ViTables installed? conda-forge package, wheel, source, cloned repo?

@uvemas
Copy link
Owner

uvemas commented Aug 27, 2017

After a long time there is no feedback from the original poster so I assume the problem has been fixed and close the bug (although I'd like to know what is the solution of the problem. That info could be useful for other users).

@uvemas uvemas closed this as completed Aug 27, 2017
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

No branches or pull requests

2 participants