# Release of PyExasol 1.0.0

**URL:** <https://community.exasol.com/t/release-of-pyexasol-1-0-0/213>\
**Category:** General\
**Tags:** integration\
**Created:** [September 1, 2025, 10:38am UTC](https://community.exasol.com/t/release-of-pyexasol-1-0-0/213 "2025-09-01T10:38:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ariel\_Schulz](https://sea2.discourse-cdn.com/flex002/user_avatar/community.exasol.com/ariel_schulz/32/61_2.png) [@Ariel\_Schulz](https://community.exasol.com/u/Ariel_Schulz)\
**Post date:** [September 1, 2025, 10:38am UTC](https://community.exasol.com/t/release-of-pyexasol-1-0-0/213/1 "2025-09-01T10:38:55Z")

</div>

We’re thrilled to announce the milestone release of PyExasol 1.0.0, marking an evolution in our Python driver for Exasol databases! This major release brings security improvements and improved, multi-version documentation.

**Security Improvements:**

- **Strict certificate validation** - the default behavior of `ExaConnection` and `pyexasol.connect` now uses strict certificate verification (`{"cert_reqs": ssl.CERT_REQUIRED}`).

- **http\_transport update** - we updated our `http_transport` methods for `IMPORT` and `EXPORT` queries to include the `PUBLIC KEY` from PyExasol’s self-signed certificate for TLS certificate validation, ensuring secure data transfer. This is an improved security feature supported since Exasol version 8.32.0 and the enacted default behavior of version 2025.1.0.

**Code & Documentation Improvements:**

- **http\_transport update** - all values within the `import_params` and `export_params` are evaluated. This makes it more transparent which parameters to `IMPORT` and `EXPORT` PyExasol supports, as described in its [Parameters page](https://exasol.github.io/pyexasol/master/user_guide/exploring_features/import_and_export/parameters.html), and gives useful feedback to the user in the event of misspelled parameter names.

**Help for Breaking Changes:**

- Users who do _not_ have PyExasol pinned to be \< 1.0.0 and were _not_ explicitly setting the SSL options are likely to experience breaking changes. This is because the previous default behavior was to not require strict certificate validation (`{"cert_reqs": ssl.CERT_NONE}`). To determine which encryption and security measures are appropriate for your organization, please read through our [Security page](https://exasol.github.io/pyexasol/master/user_guide/configuration/security.html) and update your connections appropriately.

For more details and tips on the PyExasol 1.0.0 release, please refer to our [release announcement](https://github.com/exasol/pyexasol/releases/tag/1.0.0).

---

<div class="post-metadata">

**Author:** ![Ariel\_Schulz](https://sea2.discourse-cdn.com/flex002/user_avatar/community.exasol.com/ariel_schulz/32/61_2.png) [@Ariel\_Schulz](https://community.exasol.com/u/Ariel_Schulz)\
**Post date:** [September 1, 2025, 10:42am UTC](https://community.exasol.com/t/release-of-pyexasol-1-0-0/213/2 "2025-09-01T10:42:11Z")

</div>

The release announcement can be found at:

> **[Release 1.0.0 · exasol/pyexasol](https://github.com/exasol/pyexasol/releases/tag/1.0.0)**
>
> 1.0.0 - 2025-09-01
> Summary
> Documentation update
> This release comes with updated documentation. In particular, the user guide now guides
> the user through installation, configuration, and PyExasol's ...

---

<div class="post-metadata">

**Author:** ![Ariel\_Schulz](https://sea2.discourse-cdn.com/flex002/user_avatar/community.exasol.com/ariel_schulz/32/61_2.png) [@Ariel\_Schulz](https://community.exasol.com/u/Ariel_Schulz)\
**Post date:** [September 3, 2025, 9:36am UTC](https://community.exasol.com/t/release-of-pyexasol-1-0-0/213/3 "2025-09-03T09:36:20Z")

</div>

For users that were using fingerprint verification, we’ve provided a patch with [PyExasol 1.0.1](https://github.com/exasol/pyexasol/releases/tag/1.0.1) so that the default certificate verification will be turned off for this use case.