> On Mar 9, 2016, at 22:42 , Martin Bähr <[email protected]> > wrote: > copy the script to ~/bin/ or to /usr/local/bin/ which should be in the PATH
> On Mar 9, 2016, at 22:53 , W. Trevor King <[email protected]> wrote: > $ python my/script.py These are both good suggestions that would probably help for the two-day workshops, but they somewhat defer the problem. Many students are not going to have permissions to write to /usr/local/bin, or they won’t have a ~/bin folder or it won’t be in the path (I can’t and I don’t on most of the systems i connect to) so they will have to learn sudo or sudo chmod or check the PATH anyway to make sure. Stating the interpreter and full path is also reasonable for the class, and "some of my best friends" use this as their permanent solution. For our materials we are trying to set them up with a long-term solution that would be most useful in real life. Admittedly it might not be optimized for getting them up and running when you don’t have a captive audience, and when they need to move on to other topics quickly. Truly, though, it has not been that much of an issue in long-form classes I’ve taught. -Steve _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
