Closed agruzinov closed 4 months ago
Hi @agruzinov. The DESY specific hardware objects look fine to me. Maybe additional cleaning could be to use super(). instead of super(classname, self), but this depends on you. I am concerned about the recursion you mention and find important to understand why and where it happens. Also thanks to you changing the Beamline.py, we've spotted a bug, which is very unlikely to happen, but still it is nice to have a clean code. I would not merge yet the PR, until we understand the recursion problem.
Thanks everyone for the review and comments. Would it make sense to split this PR now into HO/DESY part and abstract ones since DESY specific hardware objects are ok for everyone?
Digging into recursion problem might take more time.
Yes, @agruzinov, very good idea. We could merge your local HO and than try to find the origin of the recursion and the problem with the sample changer
@agruzinov, did I understand you correctly, that you wanted to close this PR ?
Yes, as soon as #859 will be merged. I've manually merged all the HO objects, so no-one need to go through >160 commits in the history.
:), thanks thats thoughtfull of you ;)
This PR was split to two (PR856, 859) as discussed. Closing.
Here is a repeat of PR 800, hopefully without rebase issues and updated to the current state.