On 06/24/2017 11:53 AM, Thomas Jollans wrote: > If the data is modified in-place, maybe it makes sense to to use a class > like the one you have, but then it's a bit bizarre to make your methods > create an artificial side effect (self._a_dirty) - why don't you simply > check for the actual effect of a(), whatever it is. If a() did some > calculations and added a column to your dataset with the results, check > for the existence of that column in b()! If calling b() invalidates some > calculation results generated in c(), delete them! (In the functional > setup above, b() would refuse to process a dataset that it has already > processed) > > -- Thomas > > Thanks I like this a lot! This does fit in well with my setup and I think it probably is the cleanest approach. It also makes it pretty obvious to tell where in the process you are by just looking at the data (though this is more of a convenience for myself than anyone else since the internal steps are hidden).
Thanks a lot! Cheers, Thomas -- https://mail.python.org/mailman/listinfo/python-list
