![](https://secure.gravatar.com/avatar/2e392d2cb3583602767a406c5820c63a.jpg?s=120&d=mm&r=g)
Lots of great discussion but I'm losing track of our list, so I've moved it to a google doc. Please suggest amendments so that we can get a final list together to vote on before we turn to finding volunteers to help build it. Then we will take it to a testing phase to get feedback from real learners!
https://docs.google.com/document/d/1rXM2-Up59PbOEXqZHbo_jj-zPFkhc---kVVMinPp...
Thanks,
Carrie Anne.
On Wed, Sep 23, 2015 at 12:48 AM, Dave Ames <david.john.ames@gmail.com> wrote:
On Tue, 22 Sep 2015 20:50 Nicholas H.Tollervey <ntoll@ntoll.org> wrote:
On 22/09/15 17:46, Dave Ames wrote:
I would suspect that (rightly or wrongly) most school network technicians would be extremely wary of giving students access to a system shell of any kind.
Then most school network technicians are fools and should not have ANY input in such decisions.
NOTE: I'm highly biased about this. ;-)
N.
Pythonedu-wg mailing list Pythonedu-wg@python.org https://mail.python.org/mailman/listinfo/pythonedu-wg
Absolutely no disagreement from me there. If they've configured everything correctly then access to the command line for students, should present absolutely no threat to the network. But!
The default state is "no command line", even though access to Python/Idle probably gives them at least the same level (if not more) of danger.
Dave
-- Education Pioneer Raspberry Pi Foundation
UK Charity No. 1129409