-
Notifications
You must be signed in to change notification settings - Fork 293
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
exceeding maximum number of tries #465
Comments
I have precisely the same error message for a similar piece of code. Note, however, that if I run it using a Google Colab notebook, it does work. I hope it helps :) |
Is there any solution for this.? raise MaxTriesExceededException("Cannot Fetch from Google Scholar.") |
Have you tried running this with |
Yes, it is the same error with this code snippet that uses FreeProxy: from scholarly import ProxyGenerator, scholarly
pg = ProxyGenerator()
pg.FreeProxies()
scholarly.use_proxy(pg)
query = scholarly.search_author('james watson')
author = scholarly.fill(next(query), ['publications'])
|
Tested again today. Same errors persist both with and without using a proxy. |
I just ran into the same error. |
Same error on my end, but I got it running again by upgrading |
Thank you @jkbren I can confirm that I was getting the error, and after updating Closing the issue for now, but if the issue persists even after upgrading |
I upgraded to fake-useragent 1.1.1, free-proxy 1.0.6, and scholarly 1.7.6 but the same |
Do you still get the exactly same errors on both machine 1 and 2 as you initially posted? |
I am also having this, the problem is that the (equivalent) of Try to tweak the |
@arunkannawadi yes here is the other machine: today I deleted and re-created its virtualenv for scholarly, but the error persists both with and without a proxy. Here's the environment packages list:
And the error again:
|
same problem for me btw! |
I can confirm that from my home proxy and with import requests
resp = requests.get("https://scholar.google.com/citations?hl=en&view_op=search_authors&mauthors=james%20watson")
if resp.status_code != 200:
print(f"Request failed with {resp.status_code} because {resp.reason}") I could try to experiment with |
Thanks for looking into this. |
I have updated to 1.7.10 and the error no longer happens. |
Thank you for confirming. This issue must have been fixed since 1.7.8. I'll close this issue now. To answer your earlier question, I do not understand how Google Scholar detects requests, but it was not responding to any requests sent from Python's |
Confirmed working for me now as well. |
Problem still exists when I'm using colab, here is my code: |
@syheliel please read our documentation. You're running queries that Google Scholar actively blocks without using proxies, which can get your IP address banned temporarily. |
Hi @arunkannawadi, @gboeing , @zhubonan ,
I am using scholarly 1.7.11, Ubuntu 2022, Python 3.10. The code I'm trying is the simplest:
Is anyone able to help here ? |
Yes I can confirm the error persists after upgrading both I am on Windows 7, Python 3.8, scholarly 1.7.11, fake_useragent 1.1.3 Side question: is it possible to get scholarly version from code? (tried PS - FWIW, I think updating |
Describe the bug
I have a simple script that runs once a week for to collect citation counts. It has always worked, until last night, when it started failing with the error detailed below. I have tried several times over several hours on multiple machines.
To Reproduce
I have two machines. The following code fails with different errors on the different machines.
Error on machine 1 (ubuntu, python 3.9, scholarly 1.7.5):
Error on machine 2 (ubuntu, python 3.11, scholarly 1.7.5)::
Expected behavior
I expected the code to succeed without error, like it used to.
Screenshots
n/a
Desktop (please complete the following information):
(see my platform and version details above in reproduction section)
Do you plan on contributing?
Your response below will clarify whether the maintainers can expect you to fix the bug you reported.
Additional context
n/a
The text was updated successfully, but these errors were encountered: