2. Use ophyd.v2 namespace
Date: 2022-02-18
Status
Accepted
Context
The current Ophyd needs to work alongside the new Ophyd to allow a gradual adoption. There are 2 options:
Make a new module that supercedes Ophyd
Move the current namespace to v1, importing from the top level by default, and put the new code in v2.
Decision
Decided on 2.
Consequences
In order to support this we will create a shim that uses aioca rather than pyepics for ophyd.v1 devices.