-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
syntax erroe #42
Comments
I just ran Sherlock and got no error. Try cloning the repo again and run it again. Because I did merge a PR a few hours ago and that might have fixed that syntax error. Make sure that you are using Python 3.6 or higher |
It might be good to check that merge because the change in #8 is now no longer there (and perhaps others as well). |
I added "enforce utf-8 encoding when we open data.json" (#8) back in. I
tried looking thru the merge, and did not find anything else. But, the
parallel queries really changed the structure, so I am not confident.
…On Sun, Dec 30, 2018 at 8:07 AM Simeon Visser ***@***.***> wrote:
It might be good to check that merge because the change in #8
<#8> is now no longer there
(and perhaps others as well).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABlvSMNlfZNtEbc0oHL4DY4rV8FmC0f7ks5u-MiRgaJpZM4Zk1ON>
.
|
That happened to me when I tried to execute the script with python 2.7 |
Only Python 3.6+ is supported. Python 2.7 will not work. |
@Whitedevil2002 Is this issue fixed? If fixed, can we close this? |
I think that this issue has been addressed. Pretty sure that it was caused by running Sherlock with Python 2.7. In any case, there has been quite a bit of development since this issue was entered, and any past problem would be completely changed by now. But, please reopen if still relevant. |
there is a syntax error in the file sherlock.py in line 17.
please review.
thank you!
The text was updated successfully, but these errors were encountered: