@seanpearsonuk @prmukherj A thought: if we are reorganizing what belongs in session vs fluent_connection, wouldn't it be a good idea to remove __dir__ and __getattr__ exposure as well? Specifically this code block:

pyfluent/src/ansys/fluent/core/session.py

Lines 230 to 248 in 642d73c

	def __getattr__(self, attr):
	if attr == "root":
	raise RuntimeError(
	"Please use the new structure where the settings objects can be accessed directly."
	" For example: 'solver.setup' or 'solver.solution'"
	)
	if attr == "solver":
	raise RuntimeError(
	"'Solver' is the parent object."
	" Please use the new structure, where: session.solver => solver."
	)
	return getattr(self.fluent_connection, attr)
	def __dir__(self):
	return sorted(
	set(
	list(self.__dict__.keys())
	+ dir(type(self))
	+ dir(self.fluent_connection)

In my understanding there should be no need to expose everything under fluent_connection to session like this, particularly now that we are also going to have most functions under fluent_connection moved to or with new equivalents in session. IDE tools also don't seem to be able to deal with exposure like this very well, and documentation becomes more confusing with complete exposure like this too.

Great point, @raph-luc