Zachary Lentz

Chiming in a little late: I used to be a fan of mechanisms like these. However, the more I think about `bluesky` the more I like the explicit separation between...

It's likely that the run ids, the exception type, and the offending message will be enough to cover most use cases here. I'm struggling to imagine a use for the...

I'm not sure about style, but practically you want to reduce the likelihood of someone coming later and turning `assert(False)` into `assert(False, msg)` and thinking they fixed a bug.

Usually you would map safety things like this at the OS level and bypass bluesky. At LCLS we have all the operator machines configured with a hotkey (F12) that cuts...

Can I have more context about the use cases for these namespaces? I can't think of a situation where I'm assembling scans in an IPython session, so I assume I'm...

I found something interesting today (maybe a bit hacky). It's possible to add something like: ``` import sys sys.modules['bluesky.plns'] = plns sys.modules['bluesky.rplns'] = rplns ``` And then Python is tricked...

Fair enough Dan, I agree with your points. I'm planning to use this for something completely unrelated, but I noticed that this PR was still sitting open so I thought...

My first reaction to this was "that sounds really useful." Then my second reaction was "I can't think of where I would use it." Very strange. Either way, this code...

> For reference, we had previously discussed adding "write retires" into ophyd We've had engineers in the past (circa 2018?) decide to put their write retries into their `ophyd` subclasses...

To fix this, we probably need to expand the bluesky device interface definitions (and make corresponding updates in `ophyd`). Looking at https://blueskyproject.io/bluesky/hardware.html#movable-or-settable-device, we don't have any "standard" way for bluesky...