Pyexasol

Latest version: v0.27.0

Safety actively analyzes 710445 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 6

0.21.1

Not secure
- "HTTP Transport" and "Script Output" subprocess will now restore default handler for SIGTERM signal.

In some cases custom signal handlers can be inherited from parent process, which causes unwanted side effects and prevents correct termination of child process.

0.21.0

Not secure
- Default `protocol_version` is now 3.
- Dropped support for Exasol versions `6.0` and `6.1`.

These versions have reached ["end of life"](https://www.exasol.com/portal/display/DOWNLOAD/Exasol+Life+Cycle) and are no longer supported by vendor. It is still possible to connect to older Exasol versions using PyEXASOL, but you may have to set `protocol_version=1` connection option explicitly.

0.20.0

Not secure
- Send `snapshotTransactionsEnabled` attribute only if set explicitly in connection option, prepare for Exasol 7.1 release.
- Default `snapshot_transaction` connection options is now `None` (database default), previously it was `False`.

0.19.0

Not secure
- Added connection options `access_token` and `refresh_token` to support OpenID Connect in [WebSocket Protocol V3](https://github.com/exasol/websocket-api/blob/master/docs/WebsocketAPIV3.md).
- PyEXASOL default protocol version will be upgraded to `3` if connection option `access_token` or `refresh_token` were used.

0.18.1

Not secure
- Fixed orphan process check in HTTP Transport being enabled on Windows instead of POSIX OS.

0.18.0

Not secure
- Enforced TCP keep-alive for HTTP transport connections for Linux, MacOS and Windows. Keep-alive is required to address [Google Cloud firewall rules](https://cloud.google.com/compute/docs/troubleshooting/general-tips#communicatewithinternet) dropping idle connections after 10 minutes.

Page 3 of 6

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.