Tony Locke

I'm a big fan of Flake8 Import Order, so since it looks like this project may be archived or go into maintenance-only, I've written Flake8 Alphabetize https://github.com/tlocke/flake8-alphabetize. It's designed to...

Hi @bnaoki, there wasn't really a good way of doing this, but I thought there really should be, so in release 1.28.0 the `stream` parameter can now be an iterable...

To answer your question, the `BytesIO` object represents an I/O stream, so it can't be used as an item in the iterable that is given to pg8000, because for that,...

Hi @luciengaitskell, thanks for the bug report. As it says, this type of error is usually caused by a network error, some problem with the underlying connection between the client's...

That's interesting, does every SQL statement give an error when it's run, or just the one you've shown? Also it might be worth raising the problem with Google Cloud SQL...

My guess is that the query that gives the problem is a long-running one, is that right? So I suspect that something is closing the connection if there hasn't been...

The SQL you're executing doesn't have any parameters, is that right? In that case, as long as you'renot connecting over SSL, the communication over the network should be bit-for-bit identical....

Another thought is if you are able to write a test case that reliably reproduces the problem then I can the bug as well and should be able to fix...

Hi @daveandtaye, thanks for reporting the bug. In order to work out what's going on it would help if you could post a [Minimum Reproducible Example ](https://stackoverflow.com/help/minimal-reproducible-example). Thanks!

I see the error now, before 1.22.0 the types of each parameter were specified by pg8000, and so for example if a float were sent then postgres would know it...