ckreibich / scholar.py

A parser for Google Scholar, written in Python
2.11k stars 777 forks source link

Empty result #69

Closed arcoyk closed 7 years ago

arcoyk commented 8 years ago

The result is empty now. I've confirmed the results have been ok about a week ago. I've also checked it with different network. Google Scholar may has been updated.

eknoes commented 8 years ago

What is your query? For me it works without any changes, can not verify the described behaviour

patrickallo commented 8 years ago

I have a similar issue: empty results even with the example-queries (after successful uses on the same day). Haven't been able to fix it, but it seems that the send_query method of ScholarQuerier ends up with None (leading to return) instead of parsing the html.

Update: Problem (in my case) is the following exception

HTTP Error 503: Service Unavailable

while calling _get_http_response

samerabdo commented 8 years ago

No result obtain for citation with bt or en

scholar.py -c 1 --author "albert einstein" --phrase "quantum theory" --citation bt no error message, but empty result.

the ordinary command without citation work. scholar.py -c 1 --author "albert einstein" --phrase "quantum theory"

I think the problem in adjusting "google setting" thought python.

I have suggestion about bibtex citation, it will be greatful and also easy to extract information from "import into BibTex" by making python script goes directly to link "import into BibTex"

thanks

Mengli-Shu commented 7 years ago

I have the same problem.

scholar.py -c 1 --author "albert einstein" --phrase "quantum theory" It even worked 1 h ago, and suddenly stopped working after I added the paging function and tried to print the results.

falematte commented 7 years ago

I have the same problem! No result obtain for citation with bt or en... The ordinary command without citation work.

ckreibich commented 7 years ago

Hi folks, when you see a HTTP Error 503: Service Unavailable (when using debugging output, e.g. with -ddd) then it means that the server didn't like the response. There are two possible reasons: scholar.py has become outdated and no longer accepts the query, or you've exceeded Google's acceptable rate limit. The former happens relatively rarely (thank you Google!). You can find out whether the latter is to blame by running the same query from a different IP address, if you have one available.

Also, always use the --cookie-file option to specify a cookie textfile. Just say --cookie-file ~/.scholar-cookies.txt or some such. This makes your set of queries appear more browser-like, and reduces the query rate limit problem for me.

I don't think there's an actual bug here, so please let me close this.

jiequancui commented 1 year ago

Hi,

Thanks for your work! How can I get a cookie file when I use the --cookie-file?

Best,