Hi,
I don't know if I ever wrote this down explicitly, but here it is (I'll
copy it to the FAQ later):
1) It is very hard to get this right. You can easily check Python code
(with dependencies), but checking into compiled C is harder. If the
system runs any command line programmes you need to check for them
(including libraries) as well as any configuration/datafiles they touch.
You can do this by monitoring the programmes, but it is no longer
portable (I could probably figure out how to do it on Linux, but not
other operating systems) and it is a lot of work.
It would also slow things down. Even if it checked only the Python code:
it would need to check the function code & all dependencies + global
variables at the time of task generation.
2) I was also afraid that this would make people wary of refactoring
their code. If improving your code makes jug recompute 2 hours of
results, then you wouldn't do it.
3) Jug supports explicit invalidation with jug invalidate. This checks
your dependencies.
HTH
Luis
> --
> You received this message because you are subscribed to the Google
> Groups "jug-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
jug-users+...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.