Status: To Do
Fix Version/s: None
While working on replacing Calib with PhotoCalib, I noticed the various hasXxx methods in ExposureInfo. It's not clear that these have any real utility: they're just checking whether the shared_ptr is null. Jim Bosch suggested that "we should either remove all or none of them", and "all" is out of scope for
DM-10156. We should be able to deprecate all of these.
Since we can just check that the returned property is None, the `hasX` methods don't really gain anything in python. There are some uses in C++ that might have to be refactored.
I think all the C++ usage is similarly easy, because None <=> nullptr in all of these cases. That said, I don't really see us prioritizing this and I have no plans to make an RFC for it. Anyone watching who really wants it is welcome to, but if this comes back to the CCB one more time I think we just Won't Fix it.
We use hasWcs and hasPsf in a few places outside of afw tests. We don't really use the others. We did add a new hasX method last year for hasSummaryStats. Removing all usage doesn't seem like a lot of work. This would need an RFC.