Several tests for Python 3.5.0 failed. 
The install is a local one on a shared virtual server from bluehost.com
This is a local user install, with a prefix in $HOME/python directory. 
Output of uname -a:
Linux box874.bluehost.com 3.12.35.1418868052 #1 SMP Wed Dec 17 20:04:02 CST 2014 x86_64 x86_64 x86_64 GNU/Linux

It would seem that there are no permissions to spawn() a new process, and to write temporary files to /tmp

The tests should be able to work on a virtual server, or the test should check if there are permissions to fork a process and write to a system-wide temporary directory. Of course many installations use Python on virtual hosts and often the system-wide default installation on Linux systems is 2.7.0. The tests need to fail gracefully or accommodate the lack of permissions for to fork new processes and write to system-wide temporary directories.

I've only scanned the first couple of test failures in your attachment, but they don't seem to have anything to do with spawn or /tmp.

May be /tmp is mounted on a filesystem that forbids setting the execution bit.

That's an interesting possibility regardless of this issue.  That's probably something the test suite *should* take into account, since as people get more careful about security that's something we could see happening more often.

Classification of test failures:

1. test_distutils, test_httpservers, test_shutil, test_subprocess - unable to run an executable or load a library from /tmp. This is likely testing issue, not a bug. We should just detect this situation and skip tests.

2. test_fcntl - likely a restriction of /tmp filesystem (if the test is passed in non-restricted environment). In this case we should just skip the test.

3. test_readline - readline initialization issue (issue19884). This is real bug that already was reported. We trying to fix it (unsuccessfully).