ansys-mechanical-core 0.11.11__tar.gz → 0.11.13__tar.gz

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: ansys-mechanical-core
-Version: 0.11.11
+Version: 0.11.13
 Summary: A python wrapper for Ansys Mechanical
 Keywords: pymechanical,mechanical,ansys,pyansys
 Author-email: "ANSYS, Inc." <pyansys.core@ansys.com>
@@ -17,44 +17,46 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Requires-Dist: ansys-api-mechanical==0.1.2
-Requires-Dist: ansys-mechanical-env==0.1.8
-Requires-Dist: ansys-mechanical-stubs==0.1.5
-Requires-Dist: ansys-platform-instancemanagement>=1.0.1
-Requires-Dist: ansys-pythonnet>=3.1.0rc2
+Requires-Dist: ansys-mechanical-env==0.1.9
+Requires-Dist: ansys-mechanical-stubs==0.1.6
+Requires-Dist: ansys-pythonnet>=3.1.0rc6
 Requires-Dist: ansys-tools-path>=0.3.1
 Requires-Dist: appdirs>=1.4.0
 Requires-Dist: click>=8.1.3
-Requires-Dist: clr-loader==0.2.7.post0
+Requires-Dist: clr-loader>=0.2.6
 Requires-Dist: grpcio>=1.30.0
 Requires-Dist: protobuf>=3.12.2,<6
-Requires-Dist: psutil==6.1.1
+Requires-Dist: psutil>=6
 Requires-Dist: tqdm>=4.45.0
 Requires-Dist: requests>=2,<3
 Requires-Dist: sphinx==8.1.3 ; extra == "doc"
-Requires-Dist: ansys-sphinx-theme[autoapi]==1.2.4 ; extra == "doc"
-Requires-Dist: grpcio==1.69.0 ; extra == "doc"
-Requires-Dist: imageio-ffmpeg==0.5.1 ; extra == "doc"
-Requires-Dist: imageio==2.36.1 ; extra == "doc"
+Requires-Dist: ansys-sphinx-theme[autoapi, changelog]==1.3.1 ; extra == "doc"
+Requires-Dist: grpcio==1.70.0 ; extra == "doc"
+Requires-Dist: imageio-ffmpeg==0.6.0 ; extra == "doc"
+Requires-Dist: imageio==2.37.0 ; extra == "doc"
 Requires-Dist: jupyter_sphinx==0.5.3 ; extra == "doc"
 Requires-Dist: jupyterlab>=3.2.8 ; extra == "doc"
 Requires-Dist: matplotlib==3.10.0 ; extra == "doc"
-Requires-Dist: numpy==2.2.1 ; extra == "doc"
+Requires-Dist: numpy==2.2.2 ; extra == "doc"
 Requires-Dist: numpydoc==1.8.0 ; extra == "doc"
 Requires-Dist: pandas==2.2.3 ; extra == "doc"
-Requires-Dist: panel==1.5.5 ; extra == "doc"
-Requires-Dist: plotly==5.24.1 ; extra == "doc"
-Requires-Dist: pypandoc==1.14 ; extra == "doc"
+Requires-Dist: panel==1.6.0 ; extra == "doc"
+Requires-Dist: plotly==6.0.0 ; extra == "doc"
+Requires-Dist: pypandoc==1.15 ; extra == "doc"
 Requires-Dist: pytest-sphinx==0.6.3 ; extra == "doc"
 Requires-Dist: pythreejs==2.4.2 ; extra == "doc"
 Requires-Dist: pyvista>=0.39.1 ; extra == "doc"
 Requires-Dist: sphinx-autobuild==2024.10.3 ; extra == "doc"
-Requires-Dist: sphinx-autodoc-typehints==3.0.0 ; extra == "doc"
+Requires-Dist: sphinx-autodoc-typehints==3.0.1 ; extra == "doc"
 Requires-Dist: sphinx-copybutton==0.5.2 ; extra == "doc"
 Requires-Dist: sphinx_design==0.6.1 ; extra == "doc"
 Requires-Dist: sphinx-gallery==0.18.0 ; extra == "doc"
-Requires-Dist: sphinx-notfound-page==1.0.4 ; extra == "doc"
+Requires-Dist: sphinx-notfound-page==1.1.0 ; extra == "doc"
 Requires-Dist: sphinxcontrib-websupport==2.0.0 ; extra == "doc"
 Requires-Dist: sphinxemoji==0.3.1 ; extra == "doc"
+Requires-Dist: ansys-platform-instancemanagement>=1.0.1 ; extra == "pim"
+Requires-Dist: rpyc==6.0.1 ; extra == "rpc"
+Requires-Dist: toolz==1.0.0 ; extra == "rpc"
 Requires-Dist: pytest==8.3.4 ; extra == "tests"
 Requires-Dist: pytest-cov==6.0.0 ; extra == "tests"
 Requires-Dist: pytest-print==1.0.2 ; extra == "tests"
@@ -67,6 +69,8 @@ Project-URL: Homepage, https://github.com/ansys/pymechanical
 Project-URL: Issues, https://github.com/ansys/pymechanical/issues
 Project-URL: Repository, https://github.com/ansys/pymechanical
 Provides-Extra: doc
+Provides-Extra: pim
+Provides-Extra: rpc
 Provides-Extra: tests
 Provides-Extra: viz
 
@@ -141,16 +145,17 @@ session must be reachable from your Python program.
 Getting started
 ---------------
 
+.. _scripting_guide: https://ansyshelp.ansys.com/Views/Secured/corp/v251/en/act_script/act_script.html
+
 PyMechanical uses the built-in scripting capabilities of Mechanical. For information on the
-scripting APIs available, see the `Scripting in Mechanical Guide
-<https://ansyshelp.ansys.com/Views/Secured/corp/v242/en/act_script/act_script.html>`_ in the
+scripting APIs available, see the `Scripting in Mechanical Guide <_scripting_guide>`_ in the
 Ansys Help.
 
 Configuring the mechanical installation
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 On a Windows system, the environment variable ``AWP_ROOT<ver>`` is configured when Mechanical is
-installed, where ``<ver>`` is the Mechanical release number, such as ``242`` for release 2024 R2.
+installed, where ``<ver>`` is the Mechanical release number, such as ``251`` for release 2025 R1.
 PyMechanical automatically uses this environment variable (or variables if there are multiple
 installations of different versions) to locate the latest Mechanical installation. On a Linux
 system, you must configure the ``AWP_ROOT<ver>`` environment variable to point to the
@@ -195,8 +200,23 @@ on Windows and Linux for version 2023 R2 and later. Here is an example:
    app.update_globals(globals())
    project_dir = DataModel.Project.ProjectDirectory
 
-Documentation and issues
-------------------------
+How to report issues
+--------------------
+
+If you encounter any issues or limitations with PyMechanical that hinder your work, please create
+an issue or discussion so our team can address them promptly:
+
+* `PyMechanical Issues <https://github.com/ansys/pymechanical/issues>`_: Report bugs and request new features.
+* `PyMechanical Discussions <https://github.com/ansys/pymechanical/discussions>`_: Post questions, share ideas, and get community feedback.
+
+For issues pertaining to `Mechanical scripting <https://mechanical.docs.pyansys.com/version/stable/user_guide_scripting/index.html>`_,
+please make a post on the `Developer Portal <https://forum.ansys.com/categories/structures>`_.
+
+If you have general questions about PyAnsys or are unsure which repository to place an issue in,
+email `pyansys.core@ansys.com <pyansys.core@ansys.com>`_.
+
+Documentation resources
+-----------------------
 
 Documentation for the latest stable release of PyMechanical is hosted at `PyMechanical documentation
 <https://mechanical.docs.pyansys.com/>`_.
@@ -210,13 +230,6 @@ You can also `view <https://cheatsheets.docs.pyansys.com/pymechanical_cheat_shee
 PyMechanical cheat sheet. This one-page reference provides syntax rules and commands
 for using PyMechanical.
 
-On the `PyMechanical Issues <https://github.com/ansys/pymechanical/issues>`_ page,
-you can create issues to report bugs and request new features. On the `PyMechanical Discussions
-<https://github.com/ansys/pymechanical/discussions>`_ page or the `Discussions <https://discuss.ansys.com/>`_
-page on the Ansys Developer portal, you can post questions, share ideas, and get community feedback.
-
-To reach the project support team, email `pyansys.core@ansys.com <pyansys.core@ansys.com>`_.
-
 Testing and development
 -----------------------
 

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/README.rst

@@ -69,16 +69,17 @@ session must be reachable from your Python program.
 Getting started
 ---------------
 
+.. _scripting_guide: https://ansyshelp.ansys.com/Views/Secured/corp/v251/en/act_script/act_script.html
+
 PyMechanical uses the built-in scripting capabilities of Mechanical. For information on the
-scripting APIs available, see the `Scripting in Mechanical Guide
-<https://ansyshelp.ansys.com/Views/Secured/corp/v242/en/act_script/act_script.html>`_ in the
+scripting APIs available, see the `Scripting in Mechanical Guide <_scripting_guide>`_ in the
 Ansys Help.
 
 Configuring the mechanical installation
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 On a Windows system, the environment variable ``AWP_ROOT<ver>`` is configured when Mechanical is
-installed, where ``<ver>`` is the Mechanical release number, such as ``242`` for release 2024 R2.
+installed, where ``<ver>`` is the Mechanical release number, such as ``251`` for release 2025 R1.
 PyMechanical automatically uses this environment variable (or variables if there are multiple
 installations of different versions) to locate the latest Mechanical installation. On a Linux
 system, you must configure the ``AWP_ROOT<ver>`` environment variable to point to the
@@ -123,8 +124,23 @@ on Windows and Linux for version 2023 R2 and later. Here is an example:
    app.update_globals(globals())
    project_dir = DataModel.Project.ProjectDirectory
 
-Documentation and issues
-------------------------
+How to report issues
+--------------------
+
+If you encounter any issues or limitations with PyMechanical that hinder your work, please create
+an issue or discussion so our team can address them promptly:
+
+* `PyMechanical Issues <https://github.com/ansys/pymechanical/issues>`_: Report bugs and request new features.
+* `PyMechanical Discussions <https://github.com/ansys/pymechanical/discussions>`_: Post questions, share ideas, and get community feedback.
+
+For issues pertaining to `Mechanical scripting <https://mechanical.docs.pyansys.com/version/stable/user_guide_scripting/index.html>`_,
+please make a post on the `Developer Portal <https://forum.ansys.com/categories/structures>`_.
+
+If you have general questions about PyAnsys or are unsure which repository to place an issue in,
+email `pyansys.core@ansys.com <pyansys.core@ansys.com>`_.
+
+Documentation resources
+-----------------------
 
 Documentation for the latest stable release of PyMechanical is hosted at `PyMechanical documentation
 <https://mechanical.docs.pyansys.com/>`_.
@@ -138,13 +154,6 @@ You can also `view <https://cheatsheets.docs.pyansys.com/pymechanical_cheat_shee
 PyMechanical cheat sheet. This one-page reference provides syntax rules and commands
 for using PyMechanical.
 
-On the `PyMechanical Issues <https://github.com/ansys/pymechanical/issues>`_ page,
-you can create issues to report bugs and request new features. On the `PyMechanical Discussions
-<https://github.com/ansys/pymechanical/discussions>`_ page or the `Discussions <https://discuss.ansys.com/>`_
-page on the Ansys Developer portal, you can post questions, share ideas, and get community feedback.
-
-To reach the project support team, email `pyansys.core@ansys.com <pyansys.core@ansys.com>`_.
-
 Testing and development
 -----------------------
 

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/pyproject.toml

@@ -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-mechanical-core"
-version = "0.11.11"
+version = "0.11.13"
 description = "A python wrapper for Ansys Mechanical"
 readme = "README.rst"
 requires-python = ">=3.10,<4.0"
@@ -27,17 +27,16 @@ classifiers = [
 ]
 dependencies = [
     "ansys-api-mechanical==0.1.2",
-    "ansys-mechanical-env==0.1.8",
-    "ansys-mechanical-stubs==0.1.5",
-    "ansys-platform-instancemanagement>=1.0.1",
-    "ansys-pythonnet>=3.1.0rc2",
+    "ansys-mechanical-env==0.1.9",
+    "ansys-mechanical-stubs==0.1.6",
+    "ansys-pythonnet>=3.1.0rc6",
     "ansys-tools-path>=0.3.1",
     "appdirs>=1.4.0",
     "click>=8.1.3", # for CLI interface
-    "clr-loader==0.2.7.post0",
+    "clr-loader>=0.2.6",
     "grpcio>=1.30.0",
     "protobuf>=3.12.2,<6",
-    "psutil==6.1.1",
+    "psutil>=6",
     "tqdm>=4.45.0",
     "requests>=2,<3",
 ]
@@ -58,28 +57,28 @@ tests = [
 ]
 doc = [
     "sphinx==8.1.3",
-    "ansys-sphinx-theme[autoapi]==1.2.4",
-    "grpcio==1.69.0",
-    "imageio-ffmpeg==0.5.1",
-    "imageio==2.36.1",
+    "ansys-sphinx-theme[autoapi,changelog]==1.3.1",
+    "grpcio==1.70.0",
+    "imageio-ffmpeg==0.6.0",
+    "imageio==2.37.0",
     "jupyter_sphinx==0.5.3",
     "jupyterlab>=3.2.8",
     "matplotlib==3.10.0",
-    "numpy==2.2.1",
+    "numpy==2.2.2",
     "numpydoc==1.8.0",
     "pandas==2.2.3",
-    "panel==1.5.5",
-    "plotly==5.24.1",
-    "pypandoc==1.14",
+    "panel==1.6.0",
+    "plotly==6.0.0",
+    "pypandoc==1.15",
     "pytest-sphinx==0.6.3",
     "pythreejs==2.4.2",
     "pyvista>=0.39.1",
     "sphinx-autobuild==2024.10.3",
-    "sphinx-autodoc-typehints==3.0.0",
+    "sphinx-autodoc-typehints==3.0.1",
     "sphinx-copybutton==0.5.2",
     "sphinx_design==0.6.1",
     "sphinx-gallery==0.18.0",
-    "sphinx-notfound-page==1.0.4",
+    "sphinx-notfound-page==1.1.0",
     "sphinxcontrib-websupport==2.0.0",
     "sphinxemoji==0.3.1",
 ]
@@ -87,6 +86,13 @@ viz = [
     "ansys-tools-visualization-interface>=0.2.6",
     "usd-core==24.11",
 ]
+rpc = [
+    "rpyc==6.0.1",
+    "toolz==1.0.0",
+]
+pim = [
+    "ansys-platform-instancemanagement>=1.0.1",
+]
 
 [project.scripts]
 ansys-mechanical = "ansys.mechanical.core.run:cli"
@@ -133,6 +139,7 @@ addopts = """-ra -s --durations=0 --cov=ansys.mechanical --cov-report html:.cov/
 # addopts = """-ra -s -m 'remote_session_launch or remote_session_connect or embedding' --durations=0
 # --cov=ansys.mechanical --cov-report html:.cov/html --cov-report xml:.cov/xml --cov-report \
 # term -vv --print --print-relative-time"""
+
 testpaths = [
     "tests",
 ]

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/_version.py

@@ -40,6 +40,7 @@ except ModuleNotFoundError:  # pragma: no cover
 __version__ = importlib_metadata.version("ansys-mechanical-core")
 
 SUPPORTED_MECHANICAL_VERSIONS = {
+    251: "2025R1",
     242: "2024R2",
     241: "2024R1",
     232: "2023R2",

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/app.py

@@ -134,8 +134,7 @@ class App:
     Create App with Mechanical project file and version:
 
     >>> from ansys.mechanical.core import App
-    >>> app = App(db_file="path/to/file.mechdat", version=241, pri)
-
+    >>> app = App(db_file="path/to/file.mechdat", version=251)
 
     Disable copying the user profile when private appdata is enabled
 
@@ -182,8 +181,8 @@ class App:
             profile.update_environment(os.environ)
             atexit.register(_cleanup_private_appdata, profile)
 
-        self._app = _start_application(configuration, self._version, db_file)
         runtime.initialize(self._version)
+        self._app = _start_application(configuration, self._version, db_file)
         connect_warnings(self)
         self._poster = None
 

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/background.py

@@ -76,12 +76,21 @@ class BackgroundApp:
         """
         return BackgroundApp.__app
 
-    def post(self, callable: typing.Callable):
-        """Post callable method to the background app thread."""
+    def _post(self, callable: typing.Callable, try_post: bool = False):
         if BackgroundApp.__stopped:
             raise RuntimeError("Cannot use BackgroundApp after stopping it.")
+        if try_post:
+            return BackgroundApp.__poster.try_post(callable)
         return BackgroundApp.__poster.post(callable)
 
+    def post(self, callable: typing.Callable):
+        """Post callable method to the background app thread."""
+        return self._post(callable)
+
+    def try_post(self, callable: typing.Callable):
+        """Try post callable method to the background app thread."""
+        return self._post(callable, try_post=True)
+
     def stop(self) -> None:
         """Stop the background app thread."""
         if BackgroundApp.__stopped:

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/enum_importer.py

@@ -33,5 +33,5 @@ clr.AddReference("Ansys.ACT.Interfaces")
 
 from Ansys.ACT.Interfaces.Common import *  # noqa isort: skip
 from Ansys.Mechanical.DataModel.Enums import *  # noqa isort: skip
-
+from Ansys.ACT.Interfaces.Analysis import *  # noqa isort: skip
 import Ansys  # noqa  isort: skip

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/imports.py

@@ -55,6 +55,7 @@ def global_variables(app: "ansys.mechanical.core.App", enums: bool = False) -> t
     # When ansys-pythonnet issue #14 is fixed, uncomment above
     from Ansys.ACT.Core.Math import Point2D, Point3D
     from Ansys.ACT.Math import Vector3D
+    from Ansys.ACT.Mechanical.Fields import VariableDefinitionType
     from Ansys.Core.Units import Quantity
     from Ansys.Mechanical.DataModel import MechanicalEnums
     from Ansys.Mechanical.Graphics import Point, SectionPlane
@@ -74,6 +75,7 @@ def global_variables(app: "ansys.mechanical.core.App", enums: bool = False) -> t
     vars["Point2D"] = Point2D
     vars["Point3D"] = Point3D
     vars["Vector3D"] = Vector3D
+    vars["VariableDefinitionType"] = VariableDefinitionType
 
     if enums:
         vars.update(get_all_enums())

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/initializer.py

@@ -34,7 +34,12 @@ from ansys.mechanical.core.embedding.resolver import resolve
 INITIALIZED_VERSION = None
 """Constant for the initialized version."""
 
-SUPPORTED_MECHANICAL_EMBEDDING_VERSIONS = {242: "2024R2", 241: "2024R1", 232: "2023R2"}
+SUPPORTED_MECHANICAL_EMBEDDING_VERSIONS = {
+    251: "2025R1",
+    242: "2024R2",
+    241: "2024R1",
+    232: "2023R2",
+}
 """Supported Mechanical embedding versions on Windows."""
 
 

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/logger/__init__.py

@@ -37,7 +37,7 @@ Configuring the logger can be done using the :class:`Configuration <ansys.mechan
   from ansys.mechanical.core.embedding.logger import Configuration, Logger
 
   Configuration.configure(level=logging.INFO, to_stdout=True, base_directory=None)
-  app = mech.App(version=242)
+  app = mech.App(version=251)
 
 Then, the :class:`Logger <ansys.mechanical.core.embedding.logger.Logger>` class can be used to write messages to the log:
 

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/poster.py

@@ -25,6 +25,19 @@
 import typing
 
 
+class PosterError(Exception):
+    """Class which holds errors from the background thread posting system."""
+
+    def __init__(self, error: Exception):
+        """Create an instance to hold the given error."""
+        self._error = error
+
+    @property
+    def error(self) -> Exception:
+        """Get the underlying exception."""
+        return self._error
+
+
 class Poster:
     """Class which can post a python callable function to Mechanical's main thread."""
 
@@ -37,7 +50,26 @@ class Poster:
 
         self._poster = Ans.Common.WB1ManagedUtils.TaskPoster
 
-    def post(self, callable: typing.Callable):
+    def try_post(self, callable: typing.Callable) -> typing.Any:
+        """Post the callable to Mechanical's main thread.
+
+        This does the same thing as `post` but if `callable`
+        raises an exception, try_post will raise the same
+        exception to the caller of `try_post`.
+        """
+
+        def wrapped():
+            try:
+                return callable()
+            except Exception as e:
+                return PosterError(e)
+
+        result = self.post(wrapped)
+        if isinstance(result, PosterError):
+            raise result.error
+        return result
+
+    def post(self, callable: typing.Callable) -> typing.Any:
         """Post the callable to Mechanical's main thread.
 
         The main thread needs to be receiving posted messages

{ansys_mechanical_core-0.11.11 → ansys_mechanical_core-0.11.13}/src/ansys/mechanical/core/embedding/resolver.py

@@ -23,8 +23,8 @@
 """This is the .NET assembly resolving for embedding Ansys Mechanical.
 
 Note that for some Mechanical Addons - additional resolving may be
-necessary. A resolve handler is shipped with Ansys Mechanical on windows
-starting in version 23.1 and on linux starting in version 23.2
+necessary. A resolve handler is shipped with Ansys Mechanical on Windows
+starting in version 23.1 and on Linux starting in version 23.2
 """
 
 
@@ -36,6 +36,13 @@ def resolve(version):
     clr.AddReference("Ansys.Mechanical.Embedding")
     import Ansys  # isort: skip
 
-    assembly_resolver = Ansys.Mechanical.Embedding.AssemblyResolver
-    resolve_handler = assembly_resolver.MechanicalResolveEventHandler
-    System.AppDomain.CurrentDomain.AssemblyResolve += resolve_handler
+    try:
+        assembly_resolver = Ansys.Mechanical.Embedding.AssemblyResolver
+        resolve_handler = assembly_resolver.MechanicalResolveEventHandler
+        System.AppDomain.CurrentDomain.AssemblyResolve += resolve_handler
+    except AttributeError:
+        error_msg = f"""Unable to resolve Mechanical assemblies. Please ensure the following:
+    1. Mechanical is installed.
+    2. A folder with the name "Ansys" does not exist in the same directory as the script being run.
+    """
+        raise AttributeError(error_msg)

ansys_mechanical_core-0.11.13/src/ansys/mechanical/core/embedding/rpc/__init__.py

@@ -0,0 +1,36 @@
+# Copyright (C) 2022 - 2025 ANSYS, Inc. and/or its affiliates.
+# SPDX-License-Identifier: MIT
+#
+#
+# Permission is hereby granted, free of charge, to any person obtaining a copy
+# of this software and associated documentation files (the "Software"), to deal
+# in the Software without restriction, including without limitation the rights
+# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+# copies of the Software, and to permit persons to whom the Software is
+# furnished to do so, subject to the following conditions:
+#
+# The above copyright notice and this permission notice shall be included in all
+# copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+# SOFTWARE.
+
+"""RPC and Mechanical service implementation."""
+from .client import Client
+
+# todo - provide an implementation of Server (RemoteMechancial) that installs the below
+# from .default_server import RemoteMechanical
+#        and remove them from this import statement
+# todo - combine Server and MechanicalService
+from .server import (
+    DefaultServiceMethods,
+    MechanicalDefaultServer,
+    MechanicalEmbeddedServer,
+    MechanicalService,
+)
+from .utils import get_remote_methods, remote_method