Bump version 0.11.2

Author: pyansys-automation

CODE_OF_CONDUCT.md

@@ -0,0 +1,65 @@
+# Contributor covenant code of conduct
+
+## Pledge
+
+In the interest of fostering an open and welcoming environment,
+all contributors and maintainers pledge to making participation
+in the Ansys project and community a harassment-free experience
+for everyone, regardless of age, body size, disability, ethnicity,
+sex characteristics, gender identity and expression, level of
+experience, education, socioeconomic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Standards
+
+Examples of behavior that contribute to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual
+  attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project email
+address, posting using an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Attribution
+
+This code of conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+<https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+<https://www.contributor-covenant.org/faq>

CONTRIBUTING.md

@@ -1,15 +1,14 @@
-# Contributing
-
-We absolutely welcome any code contributions and we hope that this
-guide will facilitate an understanding of the PySystemCoupling code
-repository. It is important to note that while the PySystemCoupling software
-package is maintained by ANSYS and any submissions will be reviewed
-thoroughly before merging, we still seek to foster a community that can
-support user questions and develop new features to make this software
-a useful tool for all users.  As such, we welcome and encourage any
-questions or submissions to this repository.
-
-For contributing to this project, please refer to the [PyAnsys Developer's
-Guide](https://dev.docs.pyansys.com/). Further information about
-contributing to PySystemCoupling can be found in
-[Contributing](https://systemcoupling.docs.pyansys.com/dev/contributing.html).
+# Contribute
+
+Overall guidance on contributing to a PyAnsys library appears in the
+[Contributing] topic in the *PyAnsys developer's guide*. Ensure that you
+are thoroughly familiar with this guide before attempting to contribute to
+PySystemCoupling.
+
+The following contribution information is specific to {project-name}.
+
+[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html
+
+See the [Contribute] section for the project.
+
+[Contribute]: https://systemcoupling.docs.pyansys.com/version/dev/contributing.html

README.rst

@@ -83,22 +83,28 @@ In a standard user installation, the expectation is that only ``AWP_ROOT252`` is
 (It is also possible to provide a different version number as an argument to the ``launch()``
 function. This will affect which ``AWP_ROOT<version>`` environment variable is examined.)
 
-   **WARNING**
+   **NOTE**
 
-   Note that the following applies only to the 25 R1 release of Ansys System Coupling.
+   Releases of 0.11.0 and later of PySystemCoupling define the ``launch()`` function so that
+   its *default* behavior is consistent with service pack releases of Ansys as follows:
 
-   There is an issue with the 25 R1 release of Ansys System Coupling that prevents it from
-   working in the gRPC server mode on which PySystemCoupling depends. A small patch
-   is available that may be applied to some of the Python files in the System Coupling
-   installation. This is provided in the ``patches/`` directory of this repository and will
-   allow System Coupling 25 R1 to work with PySystemCoupling releases 0.9 and later.
+   * **24 R2** - Service Pack 5 and later
+   * **25 R1** - Service Pack 4 and later
+   * **25 R2** - Service Pack 3 and later
 
-   This issue is not present in later releases of System Coupling. If a later release
-   is available, you are recommended to use that.
+   You can still use earlier releases and service packs of Ansys System Coupling, but
+   to do so you must specify a new ``connection_type`` argument to the ``launch()``
+   function with value ``ConnectionType.LOCAL_INSECURE``. See the API documentation
+   for more information.
 
-   Alternatively, PySystemCoupling can be used with an earlier release of System Coupling by
-   setting the environment variable ``AWP_ROOT`` or specifying the version number as an
-   argument to the ``launch()`` function.
+   Note that the following applies only to the **25 R1** release of Ansys System Coupling.
+
+   There was an issue with 25 R1, earlier than the Service Pack 3 release,
+   that prevented it from working in the gRPC server mode on which PySystemCoupling
+   depends. A small patch was made available in this repository to address this issue.
+   As this issue has now been officially fixed in the Service Pack 3 release of 25 R1,
+   the patch has been removed and you are recommended to install Service Pack 3 of
+   25 R1 or the latest service pack of a later release.
 
 
 The System Coupling API is exposed to PySystemCoupling in two forms:

patches/README.txt

@@ -5,7 +5,7 @@ build-backend = "flit_core.buildapi"
 [project]
 # Check https://flit.readthedocs.io/en/latest/pyproject_toml.html for all available sections
 name = "ansys-systemcoupling-core"
-version = "0.11.1"
+version = "0.11.2"
 description = "A Python wrapper for Ansys System Coupling."
 readme = "README.rst"
 requires-python = ">=3.10,<3.14"
@@ -64,7 +64,7 @@ doc = [
 	"numpydoc==1.9.0",
 	"pypandoc==1.16.2",
 	"pytest-sphinx==0.6.3",
-	"sphinx>=8.1.3",
+	"sphinx>=8.1.3,<9.0.0",
 	"sphinx-autobuild==2024.10.3",
 	"sphinx-autodoc-typehints==3.1.0",
 	"sphinx-copybutton==0.5.2",