# Is it normal Python trace doesn't record some operation?

**URL:** https://discourse.paraview.org/t/is-it-normal-python-trace-doesnt-record-some-operation/9477
**Category:** ParaView Support
**Tags:** python
**Created:** [April 20, 2022, 2:16pm UTC](https://discourse.paraview.org/t/is-it-normal-python-trace-doesnt-record-some-operation/9477 "2022-04-20T14:16:03Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [April 20, 2022, 3:22pm UTC](https://discourse.paraview.org/t/is-it-normal-python-trace-doesnt-record-some-operation/9477/3 "2022-04-20T15:22:09Z")

</div>

> [@theodorebaltis](#):
>
> The lack of parity between Python (.py) and XML (.pvsm) state files can be pretty frustrating, in my opinion.

Python tracing and state files rely on inserting code that tells what code should be generated. As ParaView is a large application, there are unfortunately some gaps in tracing completeness. Over the years, these gaps have decreased as we make sure to add Python tracing code as new code is added to ParaView. It isn’t perfect, as you have discovered, so reports like these are helpful for identifying and fixing those gaps.

As it happens, we have an issue report for this here: [https://gitlab.kitware.com/paraview/paraview/-/issues/19636](https://gitlab.kitware.com/paraview/paraview/-/issues/19636). It will be addressed like any other bug in ParaView. For more info about that process, please see [How are features and bug fixes incorporated into ParaView?](https://discourse.paraview.org/t/how-are-features-and-bug-fixes-incorporated-into-paraview/4735)

---

_[View the full topic](https://discourse.paraview.org/t/is-it-normal-python-trace-doesnt-record-some-operation/9477)._