add a decorator that saves the code to file #589
Conversation
There was a problem hiding this comment.
2 comments inline.
Apart from that, we might want to reconsider the design of treating the saved_code as a global variable. On one hand, this means that all of the code will be saved (even the one after calling train() which is desired in case, for example when we have some convert script), but there's another concern when launching consecutive trainings (not really a concern, but if we launch Resnet18 recipe then Resnet50 recipe- unnecessary code would be logged). Don't we want just the places we imported (in the sane fashion we do for register?)
Also, would be nice to have a simple unit test, maybe just a sanity that prints some code to see nothing is broken (if it is, it also mean we'd break sg_logger and therefore training).
…orator' into feature/SG-0000_svae_to_file_decorator
No description provided.