# Redefinition referencing behavior

**URL:** <https://forum.sensmetry.com/t/redefinition-referencing-behavior/574>\
**Category:** Bug Reports\
**Tags:** automator\
**Created:** [September 8, 2026, 1:50pm UTC](https://forum.sensmetry.com/t/redefinition-referencing-behavior/574 "2026-09-08T13:50:31Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Simonas](https://yyz2.discourse-cdn.com/flex008/user_avatar/forum.sensmetry.com/simonas/32/13_2.png) [@Simonas](https://forum.sensmetry.com/u/Simonas)\
**Post date:** [September 9, 2026, 12:27pm UTC](https://forum.sensmetry.com/t/redefinition-referencing-behavior/574/5 "2026-09-09T12:27:13Z")

</div>

> [@jbussemaker](#):
>
> Since there is no `.specializes()` equivalent just for redefinition (or is there?),

In Syside v0.11 there may be!

With Syside v0.11 we are introducing `syside.query` module that contains higher level API, and one function [`specializations`](https://docs.sensmetry.com/preview/python/syside/query/#syside.query.specializations) could probably be used to do what you want.

You can get the pre-release to try out as described here: [Syside v0.11.0-rc.1: try out new features earlier](https://forum.sensmetry.com/t/syside-v0-11-0-rc-1-try-out-new-features-earlier/567)

I don’t recommend relying for this in production yet, as we have found some bugs in the pre-release that will be fixed for the final 0.11.0, so we don’t want you to accidentally become reliant on some of those hidden bugs.

---

_[View the full topic](https://forum.sensmetry.com/t/redefinition-referencing-behavior/574)._