I'm creating an application on my Boxee Dlink box written in python and which uses os.system to call out to the system.
This works on the latest beta for Mac OSX. However, on the Dlink box I just get an error code.
It applies to all the system related calls, e.g. the following doesn't work either:
In the above example I just get the following exception thrown:
[Errno 10] no child processes
I am quite disappointed in how difficult it is to develop for the Boxee box. I thought it would be much more of an open platform where I could get on the box and debug on the platform itself. Python is notoriously difficult to debug (as is any interpreted language) and developers need all the help they can get to debug and run their code on the target platform.
Why does the code behave differently on Mac and Dlink boxes? This is fundamentally wrong. Developers should not have to write the code specifically to cater for specifics of the underlying platform. The Boxee api should provide a platform independent API and abstract away all the specifics.
If this is a case of Boxee Dlink boxes locking down system calls then I would like to know how to boot the box into developer mode in order to use the box in the way I want. I paid a hefty sum of money for the box and I expect to be able to use it for my own purposes.