Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 23 additions & 3 deletions .github/workflows/ci_cd.yml
Original file line number Diff line number Diff line change
Expand Up @@ -29,19 +29,22 @@ jobs:
token: ${{ secrets.GITHUB_TOKEN }}

tests:
name: "Tests"
runs-on: windows-latest
# Preserve the Windows check names required by existing branch protection.
name: ${{ matrix.os == 'windows-latest' && format('Tests ({0})', matrix.python-version) || format('Tests ({0}, {1})', matrix.os, matrix.python-version) }}
runs-on: ${{ matrix.os }}
Comment on lines +32 to +34

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably best if we delete this workaround for branch protection. I'll change the settings myself before merging so that this doesn't have an impact

strategy:
matrix:
os: [windows-latest, ubuntu-22.04, ubuntu-24.04]
python-version: ['3.10', '3.11', '3.12', '3.13', '3.14']
fail-fast: false
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
DISPLAY: ':99'
QT_QPA_PLATFORM: offscreen
steps:
- name: Install Linux os dependencies
if: runner.os == 'Linux'
run: sudo apt install libegl1
run: sudo apt-get update && sudo apt-get install -y libegl1 libgl1 libopengl0 libxkbcommon0

- name: Setup headless display
uses: pyvista/setup-headless-display-action@v5
Expand All @@ -61,6 +64,20 @@ jobs:
python-version: ${{ env.MAIN_PYTHON_VERSION }}
dependencies: "libegl1"

mcp-linux-distros:
name: "MCP Qt integration - ${{ matrix.distro }}"
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
distro: ["quay.io/centos/centos:stream9", "fedora:40"]
steps:
- uses: actions/checkout@v7
- name: Build the supported distro test environment
run: docker build --build-arg DISTRO=${{ matrix.distro }} -f scripts/mcp-validation.Dockerfile -t apm-mcp-test .
- name: Exercise Qt, offline installation, profiles and server processes
run: docker run --rm apm-mcp-test

doc-deploy:
name: "Deploy development documentation"
runs-on: ubuntu-latest
Expand Down Expand Up @@ -251,6 +268,9 @@ jobs:
- name: Update and Install development tools - Fedora
if: contains(matrix.os, 'fedora')
run: |
# Fedora 40 is retained as a packaging target and uses archived repositories.
sed -i 's|^metalink=|#metalink=|; s|^#baseurl=http://download.example/pub/fedora/linux/|baseurl=https://archives.fedoraproject.org/pub/archive/fedora/linux/|' \
/etc/yum.repos.d/fedora.repo /etc/yum.repos.d/fedora-updates.repo
yum update -y
yum group install development-tools -y

Expand Down
4 changes: 4 additions & 0 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,10 @@ Ansys Python Manager (QT)
This is a simple cross-platform `QT <https://www.qt.io/>`_ application
you can use to install Python and (optional) PyAnsys packages.

The **PyAnsys MCPs** tab also installs and manages the public PyAnsys MCP
servers, their isolated environments, HTTP processes, and coding-agent profiles.
See the `MCP management guide <https://installer.docs.pyansys.com/version/dev/mcp.html>`_.

.. image:: images/app-image.png
:align: center
:alt: Screenshot of Python Installer application
Expand Down
11 changes: 5 additions & 6 deletions doc/source/contributing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,13 @@ Contributing
Any code contributions are welcome and it is the developer team's hope that this
guide facilitates an understanding of the ``ansys-tools-installer`` code
repository. It is important to note that while the ``ansys-tools-installer`` software
package is maintained by ANSYS and any submissions are 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.
package is maintained by ANSYS and submissions are reviewed
thoroughly before merging, community members can help answer questions
and develop features that make this software useful to all users.
Questions and submissions to this repository are welcome.

For contributing to this project, please refer to the
`PyAnsys Developer's Guide`_.

.. include:: ../../README.rst
:start-after: .. contribute_start
:start-after: .. contribute_start
3 changes: 2 additions & 1 deletion doc/source/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,5 @@

installer
contributing
user_guide
user_guide
mcp
30 changes: 15 additions & 15 deletions doc/source/installer.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Installing the ``Ansys Python Manager``

.. tab-item:: Windows

First step is installing the ``Ansys Python Manager``. In order to do so, follow the next steps.
To install the ``Ansys Python Manager``, follow these steps.

#. Download the necessary installer from the `latest available release <https://github.com/ansys/python-installer-qt-gui/releases/latest>`_.
The file should be named ``Ansys-Python-Manager-Setup-v*.exe``.
Expand Down Expand Up @@ -119,7 +119,7 @@ Installing the ``Ansys Python Manager``

Under **WSL (Windows Subsystem for Linux)**, you can install the lighter
``xterm`` instead of ``gnome-terminal``. ``mesa-libGL``, ``mesa-libEGL``,
and ``xcb-util-cursor`` are still required to display the application.
and ``xcb-util-cursor`` are still required to display the app.

#. Install **zlib** package using **wget**

Expand Down Expand Up @@ -169,7 +169,7 @@ Installing the ``Ansys Python Manager``

#. Click ``Uninstall`` button.

#. Follow the uninstaller script & provide sudo permission to uninstall the application.
#. Follow the uninstaller script & provide sudo permission to uninstall the app.

.. tab-item:: Fedora39

Expand All @@ -190,7 +190,7 @@ Installing the ``Ansys Python Manager``

Under **WSL (Windows Subsystem for Linux)**, you can install the lighter
``xterm`` instead of ``gnome-terminal``. ``mesa-libGL``, ``mesa-libEGL``,
and ``xcb-util-cursor`` are still required to display the application.
and ``xcb-util-cursor`` are still required to display the app.

#. Install **zlib** package using **wget**

Expand Down Expand Up @@ -240,19 +240,19 @@ Installing the ``Ansys Python Manager``

#. Click ``Uninstall`` button.

#. Follow the uninstaller script & provide sudo permission to uninstall the application.
#. Follow the uninstaller script & provide sudo permission to uninstall the app.


Installing Python
=================

Now, instructions on how to install Python from the ``Ansys Python Manager`` are provided.

In order to do so, just follow the upcoming steps:
To do so, follow these steps:

#. Search for the ``Ansys Python Manager`` and run it.

#. Go to the ``Install Python`` tab, and select your desired Python install, version and extra packages.
#. Go to the ``Install Python`` tab, and select your desired Python install, version, and extra packages.

#. And follow the install process.

Expand All @@ -277,26 +277,26 @@ Regarding the available Python versions, users can select among the following on

1. Conda python installation:

#. Bash scripts will be downloaded and executed on a machine directly from the official website.(https://github.com/conda-forge/miniforge?tab=readme-ov-file).
#. The installer downloads and executes Bash scripts directly from the official website (https://github.com/conda-forge/miniforge).

2. Standard python installation happens in two ways:

#. If the Debian version is 22.04 and Python 3.11 (recommended by Ansys) is specified, the installer will
automatically install the pre-compiled version of Python available within the installer.
#. If the Debian version is 22.04 and Python 3.11 (recommended by Ansys) is specified, the installer
automatically installs the pre-compiled version of Python available within the installer.

#. Otherwise, Python will be installed following these steps:
#. Otherwise, the installer follows these steps:

#. Download Python Tarball and Untar:
#. Download and extract the Python archive:

i. The Python tar file will be downloaded from the Python FTP server (https://www.python.org/ftp/python)
based on the version selected from the dropdown menu. Example: For Python version 3.12.0, the download link
i. The installer downloads the Python archive from the Python FTP server (https://www.python.org/ftp/python)
based on the version selected from the dropdown menu. For example, for Python version 3.12.0, the download link
would be here(https://www.python.org/ftp/python/3.12.0/Python-3.12.0.tar.xz).

ii. Decompress the downloaded file in the user’s cache directory.

* Configure the Source:

i. Following will be executed configure the installation:
i. Run the following command to configure the installation:

.. code:: shell

Expand Down
Loading