> > I don't think so -- the google.py code doesn't read the Google output, > > it tells your browser to read it. Big difference. (urlopen(), on the > > other hand, would be a no-no.) > > ...but I disagree with your assertion about urlopen() -- as long as the > output gets rendered directly by a browser-like interface for on-line > interactive human use, I believe there's no contravention of the ToS. > (If your assertion were correct, one wouldn't be able to write a browser > in Python. ;-) Yeah. I should probably have said "a program that uses urlopen and then parses the page it gets back for a different purpose than rendering it to a human". --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4