Hi, I favor Trevor's solution too. It avoids to explain permissions, shebang, and why you have to put a dot in front of the script name. It also transfers trivially between different interpreters.
Regarding how to organize code, this paper [1] recommends to have a "scripts" directory under version control at the root level of your project. Best, Ivan [1] http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1000424 On Thu, Mar 10, 2016 at 4:36 AM, Steven Haddock <[email protected]> wrote: > > > The reason I'm teaching this stuff is that I am encouraging our > postgrads to have a "script collection". Currently I find that most people > collect their code together with their data, without the code being under > version control. > > Exactly! thus a ~/scripts folder in your PATH and under version control… > This is really the most real-world solution. > > > P.S. just after telling students about PATH etc one of our more > experienced students managed to make their laptop unusable by setting PATH > incorrectly in their .bash_profile, so I am well aware of its dangers. > > One of my more up-voted answers on stackexchange is ways to fix that, so > it definitely happens a lot in the real world. > > > _______________________________________________ > Discuss mailing list > [email protected] > > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
