mysqlx-connector-python 9.0.0__tar.gz → 9.1.0__tar.gz

mysqlx-connector-python-9.1.0/CONTRIBUTING.md

@@ -0,0 +1,358 @@
+# Contributing Guidelines
+
+We love getting feedback from our users. Bugs and code contributions are great forms of feedback and we thank you for any bugs you report or code you contribute.
+
+## Reporting Issues
+
+Before reporting a new bug, please check [Bugs List](https://bugs.mysql.com/search.php) to see if a similar bug already exists.
+
+Bug reports should be as complete as possible. Please try and include the following:
+
+* Complete steps to reproduce the issue.
+* Any information about platform and environment that could be specific to the bug.
+* Specific version of the product you are using.
+* Specific version of the server being used.
+* Sample code to help reproduce the issue if possible.
+
+## Contributing Code
+
+Contributing to this project is easy. You just need to follow these steps.
+
+* Make sure you have a user account at [MySQL Bug Report page](https://bugs.mysql.com). You will need to reference this user account when you submit your Oracle Contributor Agreement (a.k.a. OCA).
+* Sign the Oracle Contributor Agreement. You can find instructions for doing that at the [OCA Page](https://oca.opensource.oracle.com/).
+* Develop your pull request. Make sure you are aware of the [environment requirements](https://dev.mysql.com/doc/dev/connector-python/requirements.html) for the project.
+* Validate your pull request by including tests that sufficiently cover the functionality you are adding.
+* Verify that the entire test suite passes with your code applied.
+* Submit your pull request. While you can submit the pull request via [GitHub](https://github.com/mysql/mysql-connector-python/pulls), you can also submit it directly via [MySQL Bug Report page](https://bugs.mysql.com).
+
+Thanks again for your wish to contribute to MySQL. We truly believe in the principles of open source development and appreciate any contributions to our projects.
+
+## Setting Up a Development Environment
+
+The following tips provide all the technical directions you should follow when writing code and before actually submitting your contribution.
+
+* Make sure you have the necessary [prerequisites](https://dev.mysql.com/doc/dev/connector-python/installation.html#prerequisites) for building the project and [Pylint](https://www.pylint.org/) for static code analysis.
+
+* Clone MySQL Connector/Python
+
+   ```bash
+   shell> git clone https://github.com/mysql/mysql-connector-python.git
+   ```
+
+## Coding Style
+
+Please follow the MySQL Connector/Python coding standards when contributing with code.
+
+All files should be formatted using the [black](https://github.com/psf/black) auto-formatter and [isort](https://pycqa.github.io/isort/). This will be run by [pre-commit](https://pre-commit.com) if it's configured.
+
+For C files, the [PEP 7](https://peps.python.org/pep-0007/) should be followed. A ```.clang-format``` configuration is included in the source, so you can manually format the code using the [clang-format](https://clang.llvm.org/docs/ClangFormat.html) tool.
+
+## Pre-commit Checks
+
+MySQL Connector/Python comes with a pre-commit config file, which manages Git pre-commit hooks. These hooks are useful for identifing issues before committing code.
+
+To use the pre-commit hooks, you first need to install the [pre-commit](https://pre-commit.com) package and then the git hooks:
+```bash
+    shell> python -m pip install pre-commit
+    shell> pre-commit install
+```
+
+The first time pre-commit runs, it will automatically download, install, and run the hooks. Running the hooks for the first time may be slow, but subsequent checks will be significantly faster.
+
+Now, pre-commit will run on every commit.
+
+## Running `mysql-connector-python` Tests
+
+Any code you contribute needs to pass our test suite. Please follow these steps to run our tests and validate your contributed code.
+
+Run the entire test suite:
+
+```bash
+    shell> python unittests.py --with-mysql=<mysql-dir> --with-mysql-capi=<mysql-capi-dir>
+```
+
+Example:
+
+```bash
+    shell> python unittests.py --with-mysql=/usr/local/mysql --with-mysql-capi=/usr/local/mysql
+```
+
+The tests can be configured to be launched using an external server or bootstrapping it. The former is preferred (we'll assume so moving forward).
+
+As you can see, there are several parameters that can be injected into the `unittests` module. The parameters shown above are optional, or a must if you want to run the tests with the *C extension* enabled for the `mysql.connector` module.
+
+The `with-mysql-capi` flag is needed to build the `C extension` of `mysql.connector`.
+
+Additionally, there are parameters or flags that can be provided to set values to be used when connecting to the server:
+
+* **user**: the value stored by the environment variable `MYSQL_USER` is used (if set), otherwise, `root` is used by default.
+* **password**: the value of `MYSQL_PASSWORD` is used (if set), otherwise, `empty_string` is used by default.
+* **port**: the value of `MYSQL_PORT` is used (if set), otherwise, `3306` is used by default.
+* **host**: the value of `MYSQL_HOST` is used (if set), otherwise, `127.0.0.1` (localhost) is used by default.
+
+The previous defaults conform to the standard or default configuration implemented by the MySQL server. Actually, there are many more flags available, you can explore them via `python unittests.py --help`.
+
+There are two core flags you can use to control the unit tests selection:
+
+1. **-t** which is a shortcut for **--test**. This command executes one test module provided the module name::
+
+```bash
+    $ python unittests.py --use-external-server --verbosity 2 --password=$MYPASS -t cext_cursor
+```
+
+2. **-T** which is a shortcut for **--one-test**. This command executes a particular test following a finer-grained syntax such as `<module>[.<class>[.<method>]]`:
+
+```bash
+    $ python unittests.py --use-external-server --verbosity 2 --password=$MYPASS -T tests.test_bugs.BugOra16660356
+    $ python unittests.py --use-external-server --verbosity 2 --password=$MYPASS -T tests.test_bugs.BugOra17041240.test_cursor_new
+```
+
+If you do not provide any flag regarding *control of the unit tests selection*, all available test modules will be run. Some of the available test modules are:
+
+- abstracts
+- authentication
+- bugs
+- cext_api
+- cext_cursor
+- connection
+- constants
+- conversion
+- cursor
+- errors
+- mysql_datatypes
+- network
+- optionfiles
+- pooling
+- protocol
+- qa_bug16217743
+- qa_caching_sha2_password
+- utils
+
+The list is not complete, but you can deduce and find more module names by inspecting the **tests** folder and its subfolders.
+
+
+# Running `mysqlx-connector-python` Tests
+
+Any code you contribute needs to pass our test suite. Please follow these steps to run our tests and validate your contributed code.
+
+Run the entire test suite:
+
+```bash
+    shell> python unittests.py --with-mysql=<mysql-dir> --with-protobuf-include-dir=<protobuf-include-dir> --with-protobuf-lib-dir=<protobuf-lib-dir> --with-protoc=<protoc-binary>
+```
+
+Example:
+
+```bash
+    shell> python unittests.py --with-mysql=/usr/local/mysql --with-protobuf-include-dir=/usr/local/protobuf/include --with-protobuf-lib-dir=/usr/local/protobuf/lib --with-protoc=/usr/local/protobuf/bin/protoc
+```
+
+The tests can be configured to be launched using an external server or bootstrapping it. The former is preferred (we'll assume so moving forward).
+
+As you can see, there are several parameters that can be injected into the `unittests` module. The parameters shown above are optional, or a must if you want to run the tests with the *C extension* enabled for the `mysqlx` module.
+
+The `protobuf` flags are needed to build the `C extension` of  `mysqlx`.
+
+Additionally, there are parameters or flags that can be provided to set values to be used when connecting to the server:
+
+* **user**: the value stored by the environment variable `MYSQL_USER` is used (if set), otherwise, `root` is used by default.
+* **password**: the value of `MYSQL_PASSWORD` is used (if set), otherwise, `empty_string` is used by default.
+* **mysqlx-port**: the value of `MYSQLX_PORT` is used (if set), otherwise, `33060` is used by default.
+* **host**: the value of `MYSQL_HOST` is used (if set), otherwise, `127.0.0.1` (localhost) is used by default.
+
+The previous defaults conform to the standard or default configuration implemented by the MySQL server. Actually, there are many more flags available, you can explore them via `python unittests.py --help`.
+
+There are two core flags you can use to control the unit tests selection:
+
+1. **-t** which is a shortcut for **--test**. This command executes one test module provided the module name::
+
+```bash
+    $ python unittests.py --use-external-server --verbosity 2 --password=$MYPASS -t mysqlx_connection
+```
+
+2. **-T** which is a shortcut for **--one-test**. This command executes a particular test following a finer-grained syntax such as `<module>[.<class>[.<method>]]`:
+
+```bash
+    $ python unittests.py --use-external-server --verbosity 2 --password=$MYPASS -T tests.test_mysqlx_crud.MySQLxDbDocTests
+    $ python unittests.py --use-external-server --verbosity 2 --password=$MYPASS -T tests.test_mysqlx_crud.MySQLxDbDocTests.test_dbdoc_creation
+```
+
+If you do not provide any flag regarding *control of the unit tests selection*, all available test modules will be run. Some of the available test modules are:
+
+- mysql_datatypes
+- mysqlx_connection
+- mysqlx_crud
+- mysqlx_errorcode
+- mysqlx_pooling
+
+The list is not complete, but you can deduce and find more module names by inspecting the **tests** folder and its subfolders.
+
+
+## Running `mysql-connector-python` Tests using a Docker Container
+
+For **Linux** and **macOS** users, there is a script that builds and runs a Docker container which then executes the test suite (*the C extension is built and enabled only if explicitly instructed*). This means no external dependency, apart from a running MySQL server, is needed.
+
+The script uses the environment variables described previously and introduces a few new ones. These are mostly meant to be used for configuring the Docker container itself. They allow to specify the path to a *Oracle Linux* engine image, the network proxy setup, the URL of the PyPI repository to use and whether you want the **C-EXT** enabled or not.
+
+* `BASE_IMAGE` (**container-registry.oracle.com/os/oraclelinux:9-slim** by default)
+* `HTTP_PROXY` (value of the environment variable in the host by default)
+* `HTTPS_PROXY` (value of the environment variable in the host by default)
+* `NO_PROXY` (value of the environment variable in the host by default)
+* `PYPI_REPOSITORY` (https://pypi.org/pypi by default)
+* `MYSQL_CEXT` (used to control the building of the **connector.mysql** C-EXT. If set to ``true`` or ``yes``, the extension is built, otherwise it is not)
+* `MYSQL_SOCKET` (described below)
+
+There is one additional environment variable called `TEST_PATTERN` which can be used to provide a string or a regular expression that is applied for filtering one or more matching unit tests to execute.
+
+For instance, if you want to run the test module named *cursor* you'd be using:
+
+```bash
+    $ TEST_PATTERN='cursor' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+Similarly, if you want to run all tests including the pattern *con* you'd be issuing:
+
+```bash
+    $ TEST_PATTERN='.*con.*' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+If you want to run **connector.mysql** tests related to the C-EXT functionality you could use:
+
+```bash
+    $ MYSQL_CEXT='true' TEST_PATTERN='cext.*' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+In the examples above, a standard MySQL server configuration is assumed, that's the reason the values for `MYSQL_HOST`, `MYSQL_USER` or `MYSQL_PORT` weren't specified.
+
+For **Windows** users, you can set up a suitable environment to run bash scripts by installing [Git Bash](https://git-scm.com/), and using the console it provides instead of the natives *PowerShell* or *CMD*.
+
+Similar to when the tests run on a local environment, the `MYSQL_HOST` variable is only relevant for the functional tests.
+
+On **Linux**, the variable is optional and the Docker container will run using the "host" network mode whilst tests assume the MySQL server is listening on `localhost`.
+
+On **macOS** and **Windows**, since containers run on a virtual machine, host loopback addresses are not reachable. In that case, the `MYSQL_HOST` variable is required and should specify the hostname or IP address of the MySQL server. Optionally, you can use `host.docker.internal` as `MYSQL_HOST` if you want to connect to a server hosted locally [reference](https://stackoverflow.com/questions/24319662/from-inside-of-a-docker-container-how-do-i-connect-to-the-localhost-of-the-mach).
+
+Due to some [know limitations](https://github.com/docker/for-mac/issues/483) on the macOS Docker architecture, Unix socket tests can only run on Linux. In that case, if the `MYSQL_SOCKET` variable is explicitly specified, a shared volume between the host and the container will be created as a mount point from the socket file path in the host and an internal container directory specified as a volume, where the socket file path becomes available.
+
+That being said, the following are some examples of possible use cases:
+
+* Running the test modules whose name follows the pattern `c.*` from a mac whose IP is `232.188.98.520`, and the password for `root` is `s3cr3t`. Classic protocol is listening on port `3306`:
+
+```bash
+    $ TEST_PATTERN='c.*' MYSQL_HOST='192.168.68.111' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+* Running the whole test suite from Linux with MySQL user account `docker`, and password `s3cr3t`. Classic protocol is listening on port `3308`:
+
+```bash
+    $ MYSQL_PORT='3308' MYSQL_USER='docker' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+* Same setup as before but with the **connector.mysql** C-EXT enabled:
+
+```bash
+    $ MYSQL_CEXT='true' MYSQL_PORT='3308' MYSQL_USER='docker' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+
+## Running `mysqlx-connector-python` Tests using a Docker Container
+
+For **Linux** and **macOS** users, there is a script that builds and runs a Docker container which then executes the test suite (*the C extension is built and enabled only if explicitly instructed*). This means no external dependency, apart from a running MySQL server, is needed.
+
+The script uses the environment variables described previously and introduces a few new ones. These are mostly meant to be used for configuring the Docker container itself. They allow to specify the path to a *Oracle Linux* engine image, the network proxy setup, the URL of the PyPI repository to use and whether you want the **C-EXT** enabled or not.
+
+* `BASE_IMAGE` (**container-registry.oracle.com/os/oraclelinux:9-slim** by default)
+* `HTTP_PROXY` (value of the environment variable in the host by default)
+* `HTTPS_PROXY` (value of the environment variable in the host by default)
+* `NO_PROXY` (value of the environment variable in the host by default)
+* `PYPI_REPOSITORY` (https://pypi.org/pypi by default)
+* `MYSQLX_CEXT` (used to control the building of the **mysqlx** C-EXT. If set to `true` or `yes`, the extension is built, otherwise it is not)
+* `MYSQL_SOCKET` (described below)
+
+There is one additional environment variable called `TEST_PATTERN` which can be used to provide a string or a regular expression that is applied for filtering one or more matching unit tests to execute.
+
+For instance, if you want to run the test module named *cursor* you'd be using::
+
+```bash
+    $ TEST_PATTERN='mysqlx_connection' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+Similarly, if you want to run all tests including the pattern *con* you'd be issuing:
+
+```bash
+    $ TEST_PATTERN='.*con.*' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+If you want to run **mysqlx** tests with the C-EXT enabled:
+
+```bash
+    $ MYSQLX_CEXT='true' TEST_PATTERN='mysqlx_crud' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+
+In the examples above, a standard MySQL server configuration is assumed, that's the reason the values for `MYSQL_HOST`, `MYSQL_USER` or `MYSQLX_PORT` weren't specified.
+
+For **Windows** users, you can set up a suitable environment to run bash scripts by installing [Git Bash](https://git-scm.com/), and using the console it provides instead of the natives *PowerShell* or *CMD*.
+
+Similar to when the tests run on a local environment, the `MYSQL_HOST` variable is only relevant for the functional tests.
+
+On **Linux**, the variable is optional and the Docker container will run using the "host" network mode whilst tests assume the MySQL server is listening on `localhost`.
+
+On **macOS** and **Windows**, since containers run on a virtual machine, host loopback addresses are not reachable. In that case, the `MYSQL_HOST` variable is required and should specify the hostname or IP address of the MySQL server. Optionally, you can use `host.docker.internal` as `MYSQL_HOST` if you want to connect to a server hosted locally [reference](https://stackoverflow.com/questions/24319662/from-inside-of-a-docker-container-how-do-i-connect-to-the-localhost-of-the-mach).
+
+Due to some `know limitations <https://github.com/docker/for-mac/issues/483>`_ on the macOS Docker architecture, Unix socket tests can only run on Linux. In that case, if the ``MYSQL_SOCKET`` variable is explicitly specified, a shared volume between the host and the container will be created as a mount point from the socket file path in the host and an internal container directory specified as a volume, where the socket file path becomes available.
+
+That being said, the following there are some examples of possible use cases:
+
+* Running the test modules whose name follows the pattern `c.*` from a mac whose IP is `232.188.98.520`, and the password for `root` is `s3cr3t`. XDevAPI protocol listening on port `33060`:
+
+```bash
+    $ TEST_PATTERN='c.*' MYSQL_HOST='192.168.68.111' MYSQL_PASSWORD='s3cr3t' ./tests/docker/runner.sh
+```
+
+* Running the *mysqlx_crud* test module from Linux with MySQL user account `root`, and password `empty_string`. XDevAPI protocol listening on port `33070`:
+
+```bash
+    $ MYSQLX_PORT='33070' TEST_PATTERN='mysqlx_crud' ./tests/docker/runner.sh
+```
+
+
+## Test Coverage
+
+When submitting a patch that introduces changes to the source code, you need to make sure that those changes are be accompanied by a proper set of tests that cover 100% of the affected code paths. This is easily auditable by generating proper test coverage HTML and stdout reports using the following commands:
+
+1) Install the [coverage.py](https://github.com/nedbat/coveragepy) package using the following command:
+
+```bash
+    shell> python -m pip install coverage
+```
+
+2) Use coverage run to run your test suite (assuming `mysql-connector-python`) and gather data:
+
+```bash
+    shell> coverage run unittests.py --with-mysql=<mysql-dir> --with-mysql-capi=<mysql-capi-dir>
+```
+
+3) Use `coverage report` to report on the results:
+
+```bash
+    shell> coverage report -m
+```
+
+4) For a nicer presentation, use ``coverage html`` to get annotated HTML listings, The HTML will be generated in `build/coverage_html`:
+
+```bash
+    shell> coverage html
+```
+
+## Getting Help
+
+If you need help or just want to get in touch with us, please use the following resources:
+
+- [MySQL Connector/Python Developer Guide](https://dev.mysql.com/doc/connector-python/en/)
+- [MySQL Connector/Python X DevAPI Reference](https://dev.mysql.com/doc/dev/connector-python/)
+- [MySQL Connector/Python Forum](http://forums.mysql.com/list.php?50)
+- [MySQL Public Bug Tracker](https://bugs.mysql.com)
+- [Slack](https://mysqlcommunity.slack.com) ([Sign-up](https://lefred.be/mysql-community-on-slack/) is required if you do not have an Oracle account)
+- [Stack Overflow](https://stackoverflow.com/questions/tagged/mysql-connector-python)
+- [InsideMySQL.com Connectors Blog](https://insidemysql.com/category/mysql-development/connectors/)

mysqlx-connector-python-9.1.0/INFO_BIN

@@ -0,0 +1,2 @@
+build-date: 2024-09-27 12:52:58 
+os-info: Linux-5.15.0-209.161.7.2.el8uek.x86_64-x86_64-with-glibc2.28

mysqlx-connector-python-9.1.0/INFO_SRC

@@ -0,0 +1,4 @@
+version: 9.1.0
+branch: release/9.1.0
+commit: 4fbf521f1c6c71621f882f89c0c4946c10ee13ac
+short: 4fbf521

{mysqlx-connector-python-9.0.0 → mysqlx-connector-python-9.1.0}/LICENSE.txt

@@ -1,6 +1,6 @@
 Licensing Information User Manual
 
-MySQL Connector/Python 9.0.0 Community
+MySQL Connector/Python 9.1.0 Community
      __________________________________________________________________
 
 Introduction
@@ -8,18 +8,18 @@ Introduction
    This License Information User Manual contains Oracle's product license
    and other licensing information, including licensing information for
    third-party software which may be included in this distribution of
-   MySQL Connector/Python 9.0.0 Community.
+   MySQL Connector/Python 9.1.0 Community.
 
-   Last updated: May 2024
+   Last updated: September 2024
 
 Licensing Information
 
-   This release of MySQL Connector/Python 9.0.0 Community is brought to
+   This release of MySQL Connector/Python 9.1.0 Community is brought to
    you by the MySQL team at Oracle. This software is released under
    version 2 of the GNU General Public License (GPLv2), as set forth
    below, with the following additional permissions:
 
-   This distribution of MySQL Connector/Python 9.0.0 Community is designed
+   This distribution of MySQL Connector/Python 9.1.0 Community is designed
    to work with certain software (including but not limited to OpenSSL)
    that is licensed under separate terms, as designated in a particular
    file or component or in the license documentation. Without limiting

{mysqlx-connector-python-9.0.0 → mysqlx-connector-python-9.1.0}/README.rst

@@ -8,15 +8,22 @@ MySQL Connector/Python
 .. image:: https://img.shields.io/pypi/l/mysql-connector-python.svg
    :target: https://pypi.org/project/mysql-connector-python/
 
+.. === <mysql> ====
 MySQL Connector/Python enables Python programs to access MySQL databases, using
 an API that is compliant with the `Python Database API Specification v2.0
 (PEP 249) <https://www.python.org/dev/peps/pep-0249/>`_ - We refer to it as the
 `Classic API <https://dev.mysql.com/doc/connector-python/en/connector-python-reference.html>`_.
 
+.. === </mysql> ====
+
+.. === <mysqlx> [repl("It also", "MySQL Connector/Python")] ===
 It also contains an implementation of the `XDevAPI <https://dev.mysql.com/doc/x-devapi-userguide/en>`_
 - An Application Programming Interface for working with the `MySQL Document Store
 <https://dev.mysql.com/doc/refman/en/document-store.html>`_.
 
+.. === </mysqlx> ===
+
+.. === <mysql> [repl("* `XDevAPI <https://dev.mysql.com/doc/x-devapi-userguide/en>`_", "")] ====
 Features
 --------
 
@@ -25,6 +32,8 @@ Features
 * `Telemetry <https://dev.mysql.com/doc/connector-python/en/connector-python-opentelemetry.html>`_
 * `XDevAPI <https://dev.mysql.com/doc/x-devapi-userguide/en>`_
 
+.. === </mysql> ====
+
 
 Installation
 ------------
@@ -35,13 +44,17 @@ Make sure you have a recent `pip <https://pip.pypa.io/>`_ version installed
 on your system. If your system already has ``pip`` installed, you might need
 to update it. Or you can use the `standalone pip installer <https://pip.pypa.io/en/latest/installation/>`_.
 
+.. === <mysql> [repl("The *classic API* can be installed via pip as follows:", "")] ===
 The *classic API* can be installed via pip as follows:
 
 .. code-block:: bash
 
     $ pip install mysql-connector-python
 
-, similarly, the *XDevAPI* can be installed with:
+.. === </mysql> ====
+
+.. === <mysqlx> [repl("similarly, the *XDevAPI* can be installed with:", "")] ===
+similarly, the *XDevAPI* can be installed with:
 
 .. code-block:: bash
 
@@ -50,6 +63,9 @@ The *classic API* can be installed via pip as follows:
 Please refer to the `installation tutorial <https://dev.mysql.com/doc/dev/connector-python/installation.html>`_
 for installation alternatives of the XDevAPI.
 
+.. === </mysqlx> ===
+
+
 ++++++++++++++++++++
 Installation Options
 ++++++++++++++++++++
@@ -57,11 +73,15 @@ Installation Options
 Connector packages included in MySQL Connector/Python allow you to install
 optional dependencies to unleash certain functionalities.
 
+.. === <mysql> ===
 .. code-block:: bash
 
     # 3rd party packages to unleash the telemetry functionality are installed
     $ pip install mysql-connector-python[telemetry]
 
+.. === </mysql> ===
+
+.. === <mysqlx> [repl("similarly, for the XDevAPI:", "")] ===
 similarly, for the XDevAPI:
 
 .. code-block:: bash
@@ -69,10 +89,13 @@ similarly, for the XDevAPI:
     # 3rd party packages to unleash the compression functionality are installed
     $ pip install mysqlx-connector-python[compression]
 
+.. === </mysqlx> ===
+
 This installation option can be seen as a shortcut to install all the
 dependencies needed by a particular feature. Mind that this is optional
 and you are free to install the required dependencies by yourself.
 
+.. === <mysql> [repl("Options for the Classic connector:", "Available options:")] ===
 Options for the Classic connector:
 
 * dns-srv
@@ -80,12 +103,17 @@ Options for the Classic connector:
 * fido2
 * telemetry
 
+.. === </mysql> ===
+
+.. === <mysqlx> [repl("Options for the XDevAPI connector:", "Available options:")] ===
 Options for the XDevAPI connector:
 
 * dns-srv
 * compression
 
+.. === </mysqlx> ===
 
+.. === <mysql> [repl("Classic", "Sample Code"), repl("-------", "-----------")] ===
 Classic
 -------
 
@@ -113,7 +141,9 @@ Classic
     # Close connection
     cnx.close()
 
+.. === </mysql> ===
 
+.. === <mysqlx> [repl("XDevAPI", "Sample Code"), repl("-------", "-----------")] ===
 XDevAPI
 -------
 
@@ -145,7 +175,9 @@ XDevAPI
     # Close session
     session.close()
 
+.. === </mysqlx> ===
 
+.. === <both> [repl-mysql("- `MySQL Connector/Python X DevAPI Reference <https://dev.mysql.com/doc/dev/connector-python/>`_", ""), repl-mysqlx("- `MySQL Connector/Python Developer Guide <https://dev.mysql.com/doc/connector-python/en/>`_", "")] ===
 Additional Resources
 --------------------
 
@@ -157,12 +189,14 @@ Additional Resources
 - `Stack Overflow <https://stackoverflow.com/questions/tagged/mysql-connector-python>`_
 - `Oracle Blogs <https://blogs.oracle.com/search.html?q=connector-python>`_
 
+.. === </both> ===
+
 
 Contributing
 ------------
 
 There are a few ways to contribute to the Connector/Python code. Please refer
-to the `contributing guidelines <CONTRIBUTING.rst>`_ for additional information.
+to the `contributing guidelines <CONTRIBUTING.md>`_ for additional information.
 
 
 License

mysqlx-connector-python-9.1.0/SECURITY.md

@@ -0,0 +1,30 @@
+# Reporting security vulnerabilities
+
+Oracle values the independent security research community and believes that
+responsible disclosure of security vulnerabilities helps us ensure the security
+and privacy of all our users.
+
+Please do NOT raise a GitHub Issue to report a security vulnerability. If you
+believe you have found a security vulnerability, please submit a report to
+secalert_us@oracle.com preferably with a proof of concept. Please review
+some additional information on how to report security vulnerabilities to Oracle
+(see https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html)
+We encourage people who contact Oracle Security to use email encryption using
+our encryption key (see https://www.oracle.com/security-alerts/encryptionkey.html)
+
+We ask that you do not use other channels or contact the project maintainers
+directly.
+
+# Security updates, alerts and bulletins
+
+Security updates will be released on a regular cadence. Many of our projects
+will typically release security fixes in conjunction with the Oracle Critical Patch
+Update program. Additional information, including past advisories, is available on our
+security alerts page at https://www.oracle.com/security-alerts/
+
+# Security-related information
+
+We will provide security related information such as a threat model, considerations
+for secure use, or any known security issues in our documentation. Please note
+that labs and sample code are intended to demonstrate a concept and may not be
+sufficiently hardened for production use.

{mysqlx-connector-python-9.0.0 → mysqlx-connector-python-9.1.0}/mysqlx/tls_ciphers.py

@@ -29,11 +29,12 @@
 """TLS ciphersuites and versions."""
 
 # Generated from the OSSA cipher list
-# version: 3.3
-# date: 2024-01-10
+# version: 3.4
+# date: 2024-04-11
 
 from typing import Dict, List
 
+
 APPROVED_TLS_VERSIONS: List[str] = ["TLSv1.2", "TLSv1.3"]
 """Approved TLS versions."""
 
@@ -61,11 +62,6 @@ APPROVED_TLS_CIPHERSUITES: Dict[str, Dict[str, str]] = {
         "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256": "ECDHE-RSA-CHACHA20-POLY1305",
         "TLS_ECDHE_ECDSA_WITH_AES_256_CCM": "ECDHE-ECDSA-AES256-CCM",
         "TLS_ECDHE_ECDSA_WITH_AES_128_CCM": "ECDHE-ECDSA-AES128-CCM",
-        "TLS_DHE_RSA_WITH_AES_128_GCM_SHA256": "DHE-RSA-AES128-GCM-SHA256",
-        "TLS_DHE_RSA_WITH_AES_256_GCM_SHA384": "DHE-RSA-AES256-GCM-SHA384",
-        "TLS_DHE_RSA_WITH_AES_256_CCM": "DHE-RSA-AES256-CCM",
-        "TLS_DHE_RSA_WITH_AES_128_CCM": "DHE-RSA-AES128-CCM",
-        "TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256": "DHE-RSA-CHACHA20-POLY1305",
     },
     "TLSv1.3": {
         "TLS_AES_128_GCM_SHA256": "TLS_AES_128_GCM_SHA256",
@@ -79,6 +75,11 @@ APPROVED_TLS_CIPHERSUITES: Dict[str, Dict[str, str]] = {
 
 DEPRECATED_TLS_CIPHERSUITES: Dict[str, Dict[str, str]] = {
     "TLSv1.2": {
+        "TLS_DHE_RSA_WITH_AES_128_GCM_SHA256": "DHE-RSA-AES128-GCM-SHA256",
+        "TLS_DHE_RSA_WITH_AES_256_GCM_SHA384": "DHE-RSA-AES256-GCM-SHA384",
+        "TLS_DHE_RSA_WITH_AES_256_CCM": "DHE-RSA-AES256-CCM",
+        "TLS_DHE_RSA_WITH_AES_128_CCM": "DHE-RSA-AES128-CCM",
+        "TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256": "DHE-RSA-CHACHA20-POLY1305",
         "TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8": "ECDHE-ECDSA-AES256-CCM8",
         "TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8": "ECDHE-ECDSA-AES128-CCM8",
         "TLS_DHE_RSA_WITH_AES_256_CCM_8": "DHE-RSA-AES256-CCM8",

{mysqlx-connector-python-9.0.0 → mysqlx-connector-python-9.1.0}/mysqlx/version.py

@@ -32,7 +32,7 @@ The file version.py gets installed and is available after installation
 as mysqlx.version.
 """
 
-VERSION = (9, 0, 0, "", 1)
+VERSION = (9, 1, 0, "", 1)
 
 # pylint: disable=consider-using-f-string
 if VERSION[3] and VERSION[4]: