Add deprecation notice for this repository

[shubhamjain]

No description provided.

[marm123]

I'm not sure if we want to add this notice. Currently, it'll probably create even more confusion than there already is, as we're using the old library in all examples/code snippets in documentation/Playground.

Perhaps we should switch that to the new library first, what do you think @shubhamjain?

[shubhamjain]

@marm123 Are we using the this library in latest examples? In the documentation, I can see we are importing serpapi module everywhere, not google-search-results. We already have a document stating that we deprecating similar API for node.js.

The google-search-results-nodejs npm package is being deprecated in favor of the serpapi npm package. It will still be available via npm, but will not receive feature updates. The following are the differences to better help you migrate over to the serpapi npm package.

https://github.com/serpapi/serpapi-javascript/blob/master/docs/migrating_from_google_search_results_nodejs.md

[marm123]

That's part of the confusion.

The following import still uses google-search-results (reference):
from serpapi import GoogleSearch

The new library is initiated with a simple import serpapi (reference).

Because of that, both libraries can't work together, and we have many customers confused about this, which is completely understandable.

[hilmanski]

Relevant issue for reference: https://github.com/serpapi/SerpApi/issues/5277

I'm also curious if we have full control/ownership of the library (on Pypi/PIP) side, as I see Kenneth still listed as one of the maintainers: https://github.com/serpapi/serpapi-python

[shubhamjain]

@marm123 Oh my bad! thanks for letting me know.