Hi Eric.
First, to clarify our github repository situation...
gotcha
Next, in continuing work on the unit tests for proc.py, we ran into another issue with the mocking code.
Nice catch, though for your example (os.readlink) won't this make the tests platform dependent? Currently Beck (another volunteer working on stem) is working on making the tests run on Windows and it would be sad if we made his life harder. ;)
Minor gity side note, there is almost no use case where you should be merging 'remotes/torproject/master' into your branch. Either rebase onto 'remotes/torproject/master' or make a new branch on 'remotes/torproject/master' instead. That will make your dag (directed acyclic graph - the parent/child relationships between commits) far cleaner. Otherwise I need to cherry-pick rather than merge your work since merging would pull extra commits and confuse the master's dag. Let me know if you have any questions about this - admittedly without a whiteboard git can be a little confusing for new users.
Cheers! -Damian