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

import error in pypge.search #3

Open
arendsee opened this issue Mar 31, 2016 · 4 comments
Open

import error in pypge.search #3

arendsee opened this issue Mar 31, 2016 · 4 comments

Comments

@arendsee
Copy link

The import below

from pypge.search import PGE

outputs the following error message

** (pge-test.py:5235): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "./pge-test.py", line 2, in <module>
    from pypge.search import PGE
  File "/usr/lib/python3.5/site-packages/pypge/search.py", line 25, in <module>
    from websocket import create_connection
ImportError: cannot import name 'create_connection'

I believe the problem is that search.py is attempting to use a package that does not exist in python3.

Replacing

from websocket import create_connection

with

from websockets import connect

and replacing create_connection everywhere in search.py with connect, might fix the problem (I haven't looked into it very carefully yet).

@embg
Copy link

embg commented Jun 7, 2016

I have the same problem. I fixed it temporarily by commenting out the code that uses create_connection. Please fix!

@ianhbell
Copy link

ianhbell commented Jun 8, 2016

My experience is that a pip install websocket-client fixes this particular issue

@verdverm
Copy link
Owner

verdverm commented Jun 8, 2016

Probably a missing line in requirements.txt

On Tue, Jun 7, 2016, 6:06 PM Ian Bell [email protected] wrote:

My experience is that a pip install websocket-client fixes this
particular issue


You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub
#3 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ABU4CPlKJO1ytRQfCQz5I-rV-q5yaRasks5qJgeggaJpZM4H9QU4
.

@verdverm
Copy link
Owner

New instructions for running in the README.md

Let me know how this works out

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

4 participants