Dan Allan

Agreed. Dumping the `git grep` output above without comment was slapdash. The `classmethods` seem fine as is to me.

Notes from a Pilot call: Paraphrasing @tacaswell from memory > Links are fragile. If some facilities need to let users customize the file names, ophyd should add a hook to...

I think there is a fair worry there that links are fragile. The underlying files may be moved, and Data Broker can manage that seamlessly (`root_map`) but the links will...

I am in favor of doing cheap validation in `Component.__init__`. I am against strict type-checking because I think it is a feature that we can operate with other implementations that...

We may need some public API to abandon an apparently-failed set operation. This requires careful thought, because once you set something in motion in EPICS there is no recalling it,...

Will address with https://github.com/NSLS-II/bluesky/issues/716

All sounds good to me. As you would guess, we haven’t been driven to add support for newer versions by any critical backward-incompatible changes upstream, so this work has not...

The two threads from `ophyd.sim` itself generate INFO-level log messages periodically, such that `logging.basicConfig()` gets very noisy. (A downstream user reported this. We tend not to use `basicConfig()` because it's...

Now I understand. In my environment, I happen to have pyepics installed, so ophyd creates a pyepics control layer. You do not have pyepics but you do have caproto, so...

Good thought! Could we do both? That is, provide a public method but automatically call that public method when one of those methods(`get`, `put`, ...) is called? I think we'll...