(The last version I installed at work was 3.7. Not sure if this bug report is specific to 4.2b1 or anything newer than 3.7.)
I downloaded coverage 4.2b1 then packaged it up using our internal system (little more than a tar file of the install tree plus an info file.) I pushed that out, thinking that as a development tool, it would have no production impacts. Unfortunately, the install process created a site.py file (see the attached build.out file).
Python in this case is Python 2.7.2. That has been static/stable/outdated since before I first installed coverage locally, so I don't think my toolchain has changed in any meaningful way. I'm sort of guessing that the setup.py script which comes with Coverage has changed.
Why is the install process creating a site.py file? I think I can work around the problem by removing site.py and site.pyc from the /var/tmp/... install location before repackaging it, but some piece of the tool chain must have thought that creating it was a good idea. I'd kind of like to understand who was ultimately responsible for this.