That’s true. Often, I create a separate venv for each project plus manifest. I also push everything to a private git repo (next to a couple of “regular” back up solutions) — I am really paranoid when it comes to back-ups and version control :P.
> But if you didn't snapshot all libraries you are using, the code might > not run any more, or give different results ;) I this make file approach is more useful in the context of running your pipeline in cases where software gets updated, e.g,. if there was a bug in a certain package you were using, and now you want to reproduce the results with this new version to see if your previous results were affected by this bug. Or just if a colleague/reviewer wants to reproduce your stuff ;) > On Aug 24, 2015, at 5:59 PM, Andreas Mueller <t3k...@gmail.com> wrote: > > > > On 08/19/2015 12:37 AM, Sebastian Raschka wrote: >>> if the unpickling failed, >>>> what would you do? >> One lesson “scientific research” taught me is to store the code and dataset >> along with a “make” file under version control (git):). I would just run my >> make file to re-construct the model and pickle the objects. >> > But if you didn't snapshot all libraries you are using, the code might > not run any more, or give different results ;) > > ------------------------------------------------------------------------------ > _______________________________________________ > Scikit-learn-general mailing list > Scikit-learn-general@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/scikit-learn-general ------------------------------------------------------------------------------ _______________________________________________ Scikit-learn-general mailing list Scikit-learn-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
