Some people may want to add some functionality in their shells via Python coding; that is something we haven't talked about yet, and which may be important.
Python can be a source of fun but it can also be a source of bugs.
Given our model of community Age and the way shells are created and exported separately, how would Python integrate into that?
(I'm not versed at all in this subject I must confess, so I have no idea.)
What files would people need to send?
Would we need a naming convention for files, variables and functions to avoid any conflicts?
Would we need to do some work ourselve to implement everything together (dabble into files like the SDL or others) or could everything be done separately like the shells?
etc.
As always the goal would be to require minimal intervention from us, so anyone can do their stuff and almost all we have to do is to upload that to the UAM servers.
If it is too much of a headache should we simply disallow it? Or disallow it for now (since few people use it right now) and see later?