ImportError running make test in newly-cloned repo

[bhrutledge]

I started working on #64, but I immediately hit a wall running the tests before making any changes. I followed the "Hacking" instructions, and started getting errors like ImportError: 'test_factory' module incorrectly imported from '<project_dir>/.tox/py27-django18/lib/python2.7/site-packages/mail_factory/tests'. Expected '<project_dir>/mail_factory/tests'. Is this module globally installed?. This error showed up in all Tox environments for Django 1.6+. For Django 1.4 and 1.5, I didn't get the error, but I get Coverage.py warning: No data was collected.

I posted a Gist of a fresh clone and environment setup, using commands from the Makefile instead of make test to limit the output to py27-django18 and py27-django15. There's also some information about my system in there, but in short, I'm on a MacBook Air running El Capitan, with Python 2.7.12 installed via Homebrew. But, I've had the same results on another MacBook and an Ubuntu VM, both using Python 2.x and 3.x installed via pyenv.

A little Googling suggests that the ImportError might be related to symlinks in virtualenvs, but I haven't dug into it yet. I see the Travis builds are succeeding, so I'm assuming there's something about my environment that's messing things up. Have any other developers encountered this? What development environments are people using? It's worth noting that this is the first time I've attempted hacking on a PyPI package, so I'm not yet familiar with setuptools.

[bhrutledge]

I'm having the same issue on a fresh ubuntu:precise Docker container plus apt-get install python-setuptools python-dev build-essential git and easy_install pip==6.0.7 (which is what Travis seems to use).