Dear Dr. Geuzaine, I was experimenting with some features of the python API when I realised that `gmsh.model.mesh.setOrder(element_order)` and `gmsh.option.setNumber("Mesh.ElementOrder", element_order)` are inconsistent, and the related geometry is not meshed with the same element order. Is it by design? **Expected behaviour:** As per documentation of `gmsh.model.mesh.setOrder` ("Set the order of the elements in the mesh of the current model to `order'.") I would expect that the function would return 'element_order'. Is it correct or am I misinterpreting the documentation? The behaviour I was expecting is respected when using `gmsh.option.setNumber("Mesh.ElementOrder", element_order)`. **Actual Behavior:** While `gmsh.option.setNumber("Mesh.ElementOrder", element_order)` appears to correctly set the desired element order, the `gmsh.model.mesh.setOrder(element_order)` function does not seem to behave as expected. I attach below a MWE. **Tested on:** - MacOS 14.4.1 and Gmsh 4.12.2 Thank you. Best regards, Simone [test_mesh_order.py](/uploads/74daa5ac5145abb8442cf9a0c45c1ef0/test_mesh_order.py)