6.x: functionality regression from losing requests in SPARQLStore

[delocalizer]

I wish I'd noticed #1175 before it was merged to trunk and then released in 6.0.0 but anyway...

Having requests handle HTTP in SPARQLStore was powerful, and now we've lost some nice things it provided (and that we were using)

Two specific examples:

• without an underlying requests.Session attribute it's not possible to configure connection pooling, mount Retry adapters or otherwise manipulate the HTTP coms in any advanced way.

• clients no longer have access to the detailed content of the response to a bad query via raised requests.HttpError, (depending on your endpoint this may be e.g. SPARQL syntax error info) - now you just get back a tuple containing 4xx error code and a message.

on the whole I'd say this was a backwards move

[nicholascar]

We could implement httpx instead of requests for the same features and fewer dependencies perhaps…

[delocalizer]

httpx has some nice features but not sure that it has fewer dependencies than requests... in any case I'm in favour of any solution that restores support for sessions and other high-level HTTP(S) ops to sparqlconnector.SparqlConnector

For my records, the historical context to this change was #1122

[eilmiv]

I'm running into the same problem. Maybe a simple solution could be to extract the actual http request into some simple method. That way, we could easily override this method in a subclass to use requests, httpx or any custom logic if desired.