Eva Lott
Eva Lott
Once https://github.com/numpy/numpydoc/pull/542 is released, we will be able to accurately reflect return types of generators within docstrings. We should add a `Returns` section to such docstrings. There are a few...
Closes #1821
`Readable` has been made generic in #1800, we could do the same to `Movable` A device class has a `set` method that is only valid for limited argument types: writing...
Ophyd still uses older and less specific return types for some of the bluesky protocols. ``` python class SomeDevice(Device): readable_sig = Component(SignalRO, "prefix") def read_stuff(signal: Readable): pass my_device = SomeDevice("prefix",...
Would be good if this produced a `p4p.Value` instead... _Originally posted by @evalott100 in https://github.com/DiamondLightSource/FastCS/pull/119#discussion_r1963562763_
`NTTable` can be initialised with string valued columns, but strings can never be given. ``` python from p4p.server.thread import SharedPV from p4p.server import Server from p4p.nt import NTScalar, NTTable import...
Currently, both `NTScalar` and `NTEnum` allow for `extra` to be passed in on initialisation, which means additional fields can be passed in on init. These fields can be used in...
I can't get the async server to work. I think adding an example while troubleshooting this would be good. Both `READ_PV` and `WRITE_PV` can be successfully set up and `pvget`'d,...
I have a jsonschema ``` json { "title": "resource", "type": "object", "allOf": [ { "$ref": "#/$defs/PartialResource" } ], "$defs": { "PartialResource": { "title": "partial_resource", "properties": { "spec": { "title": "spec",...
# Problem In [ophyd-async](https://github.com/bluesky/ophyd-async), we want a test environment where if there are unfinished tasks after any test has finished then the test will error. We had quite a lot...