# FYI Non-visible Butler init changes

**URL:** <https://www.rubin.community/t/fyi-non-visible-butler-init-changes/1657>\
**Category:** Data Management\
**Tags:** butler, dm-dev\
**Created:** [February 22, 2017, 2:25am UTC](https://www.rubin.community/t/fyi-non-visible-butler-init-changes/1657 "2017-02-22T02:25:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![natepease](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/natepease/32/2086_2.png) [@natepease](https://www.rubin.community/u/natepease)\
**Post date:** [February 22, 2017, 2:25am UTC](https://www.rubin.community/t/fyi-non-visible-butler-init-changes/1657/1 "2017-02-22T02:25:34Z")

</div>

Just an FYI - I just checked in [DM-9039 reorder butler init to be more incremental when building Repositories](https://jira.lsstcorp.org/browse/DM-9039). It should not have any visible changes to Butler users, or any affect on the interaction between obs\_base classes and the Butler. However, if you run into problems with Butler, especially during Butler init after a rebuild of the stack, please let me know.