In this same same repo, make a separate bluesky-tiled-plugins package that contains the objects in databroker.client and their associated entrypoint declarations. These are the objects like BlueskyRun and CatalogOfBlueskyRuns that provide an optional, upgraded Python interface to Bluesky metadata/data in Tiled.
Thus, it will only be necessary to import databroker when:
Importing databroker.Broker for backward-compatible user code
Running a Tiled server with databroker.mongo_normalized
New user code can operate with just tiled and the tiny bluesky-tiled-plugins. Lightweight and easy to explain to new users.
Per discussion with @tacaswell:
In this same same repo, make a separate
bluesky-tiled-pluginspackage that contains the objects indatabroker.clientand their associated entrypoint declarations. These are the objects likeBlueskyRunandCatalogOfBlueskyRunsthat provide an optional, upgraded Python interface to Bluesky metadata/data in Tiled.Thus, it will only be necessary to import
databrokerwhen:databroker.Brokerfor backward-compatible user codedatabroker.mongo_normalizedNew user code can operate with just
tiledand the tinybluesky-tiled-plugins. Lightweight and easy to explain to new users.