Clearly mark features that require unreleased Ansys versions in the documentation

[Cerberus-ik]

Description of the modifications

Hi there, in the past days I keep running into issues with my code due to some functions requiring Ansys 2025 R2 (which has not released at the time of writing).

Examples I have run into

• bounding box
• shell_body

I would prefer to have them marked as 'unusable' or 'Ansys Beta' somewhere.

Maybe in the future py_ansys functions could not be merged into the current (stable) release but rather stay in the dev build until they are usable by the public.

On this note, is it possible to gain access to Ansys beta versions? The Download portal doesn't offer anything like that and our support rep hasn't heard of anything either.

Useful links and references

https://geometry.docs.pyansys.com/version/stable/api/ansys/geometry/core/designer/body/Body.html#Body.shell_body

[RobPasMue]

Hi @Cerberus-ik! Thanks for bringing this up to my attention.

I agree.. it's probably not that clear on the documentation. These methods (in their implementation) have a wrapper that checks whether it can be used or not with your current running version... which is probably the one throwing the error you are getting. See for example:

pyansys-geometry/src/ansys/geometry/core/designer/body.py

Lines 855 to 860 in 6f0d394

	@property
	@min_backend_version(25, 2, 0)
	def is_suppressed(self) -> bool: # noqa: D102
	response = self._grpc_client.services.bodies.is_suppressed(id=self.id)
	return response.get("result")

We should add a note to the docstrings whenever there is a min_backend_version decorator call. So that users can know from the documentation whether a method is usable or not.

Regarding your point about the Download portal, that is true.. it is not available beforehand. The good thing is that 25R2 is right around the corner :)

[RobPasMue]

Adding myself to this issue - I'll try to handle this asap.