# \[IGN-5244\]Persist Python Class Object

**URL:** <https://forum.inductiveautomation.com/t/ign-5244-persist-python-class-object/30498>\
**Category:** Ignition\
**Created:** [December 6, 2019, 5:37pm UTC](https://forum.inductiveautomation.com/t/ign-5244-persist-python-class-object/30498 "2019-12-06T17:37:15Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 17, 2022, 1:32am UTC](https://forum.inductiveautomation.com/t/ign-5244-persist-python-class-object/30498/27 "2022-02-17T01:32:55Z")

</div>

Hah. Such a good idea we already talked about it a few months ago:

> [@\[IGN-5244\]Using Class Instance as View Custom Object Property](https://forum.inductiveautomation.com/t/using-class-instance-as-view-custom-object-property/53676/3):
>
> Yeah, as Phil said, this isn’t going to work as-is. We could in theory implement something like this (it is convenient in Vision to be able to get/put arbitrary objects at runtime), but I wouldn’t expect it anytime soon, so you’ll have to work around it somehow.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ign-5244-persist-python-class-object/30498)._