Numpy 2.X and Python 3.13 support

[RobPasMue]

Hi @viseshrp @margalva - first of all, thank you both for your explanations. Much appreciated!

Based on the outcome of this PR, and starting on 0.10.3, we will have to remove PyDynamicReporting from the metapackage whenever the user requests to install it in Python 3.13.

This will look in our pyproject.toml as follows:

dependencies=[
    ...
    "ansys-dynamic-reporting==0.10.3; python_version<'3.13',
    ...
]

This is a temporary skip, since an explicit requirement on our side is supporting Python 3.13.

Important

If by the time a new metapackage release is required you still don't support Python 3.13 we will have to effectively remove you from the metapackage at large - in order to avoid delivering mixed environments wrt our own libraries (i.e. Python 3.11 containing N PyAnsys libraries, Python 3.13 containing M PyAnsys libraries -- we should always be delivering the same amount of our own libraries).

Once support for NumPy 2.x has been re-established and Python 3.13 please let us know so that we can remove this constraint from the metapackage.

Originally posted by @RobPasMue in #408 (comment)

[RobPasMue]

@viseshrp @margalva - as we have informed recently through various internal channels, there is a planned beta release of the metapackage this Friday. We have requested teams to get a release ready for it if possible, although if not that is fine and we will patch release the metapackage later.

In any case, this reminded me of the problem that was raised some months ago. I am looking for its resolution if possible. Otherwise, as we explained in the PR, we will have to drop PyDynamicReporting since not supporting Numpy 2.X is a big drag on the rest of the libraries of the ecosystem.

[RobPasMue]

Pinging @ansys/pyansys-core for visibility

[margalva]

day. We have requested teams to get a release ready for it if possible, although if not that is fine and we will patch release the metapackage later.

In any case, this reminded me of the problem that was raised some months ago. I am looking for its resolution if possible. Otherwise, as we explained in the PR, we will have to drop PyDynamicReporting since not supporting Numpy 2.X is a

The latest release we have available (from mid-December) is recent enough that it could be included in the Metapackage.
However, we still do not have a resolution for the numpy 2.X upgrade. We still need to be on 1.X versions as per flagships requirements. The RMU is planning on the numpy upgrade as part of the 27.1 cycle, so this will hopefully be solved in the next few months.

[RobPasMue]

Hi @margalva - thank you for the clarifications on your side! We understand the limitations coming from RMU and their timelines. However, PyAnsys libraries are not intended to be tight to the same requirements of the unified install - although we also acknowledge that for some of the libraries this might be the case, as it is for PyDynamicReporting.

I had a look at your last release (0.10.6) and this version also has the Numpy 2.X and Python 3.13 issue so, even if it's the latest, it is non-compliant with the requirements of the metapackage 😢.

As I mentioned back in #408 (comment) - both conditions (and especially the Python 3.13 one) are a strict requirement of the metapackage. All libraries are requested to comply with it - and we will avoid shipping environments where some libraries are available and others aren't, in order to avoid user confusion.

Once PyDynamicReporting complies with both requirements, we will be able to integrate it back into the metapackage (hopefully soon! 😃) - but for now, we will have to remove it. That doesn't mean that users can't install your package in standalone mode of course. They will be able to do so.

[MaxJPRey]

Thanks @RobPasMue for the close follow up.
@margalva it makes sense. We will wait 27.1 then for reinstating the lib in the metapackage