# Python interface command naming conversions

**URL:** <https://getfem.discourse.group/t/python-interface-command-naming-conversions/76>\
**Category:** General\
**Created:** [April 4, 2025, 4:29pm UTC](https://getfem.discourse.group/t/python-interface-command-naming-conversions/76 "2025-04-04T16:29:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Konstantinos.Poulios](https://avatars.discourse-cdn.com/v4/letter/k/ac91a4/32.png) [@Konstantinos.Poulios](https://getfem.discourse.group/u/Konstantinos.Poulios)\
**Post date:** [April 4, 2025, 4:29pm UTC](https://getfem.discourse.group/t/python-interface-command-naming-conversions/76/1 "2025-04-04T16:29:39Z")

</div>

@yves.renard

Dear Yves, I am working on adding a new mumps context object to the scripting interface, but I am a bit stuck with the object member function naming system.

In the following example for the `MeshFem` object, the `qdim` command is converted to `set_qdim`, while the `reduction matrices` command is translated to `reduction_matrices` without the “set\_” prefix.

Where is it decided on whether the “set\_” prefix is prepended or not?

 ![image](https://global.discourse-cdn.com/free1/uploads/getfem/original/1X/819168da0b245613cce8595aefcfd5683f73c472.png)

---

<div class="post-metadata">

**Author:** ![Konstantinos.Poulios](https://avatars.discourse-cdn.com/v4/letter/k/ac91a4/32.png) [@Konstantinos.Poulios](https://getfem.discourse.group/u/Konstantinos.Poulios)\
**Post date:** [April 4, 2025, 4:38pm UTC](https://getfem.discourse.group/t/python-interface-command-naming-conversions/76/2 "2025-04-04T16:38:07Z")

</div>

@yves.renard never mind it, found it in bin/extract\_doc:

> # one pass to find the set methods having identical name with a get method  
> # in that case ‘set\_’ is added to the set method.

with the only exceptions to the rule being `set_classical_...fem` functions