id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
2747	"""tox"" on debian (py3) can't run our setup.py"	warner	warner	"rkirshnan reported that running ""tox"" on current debian/testing fails. 

On that platform (as well as some Ubuntu ones I've seen), the system-packaged `/usr/bin/tox` is shbang'ed to use python3. Tox runs the project's `setup.py` to make an sdist tarball (which it then installs into the virtualenv). Tahoe's `setup.py` has a line that explicitly fails when run with python3, to avoid confusion, since Tahoe only works with python-2.7 . When tox hits this, it fails.

To fix this, I think we should take out the hard-fail. It might be good to leave in a warning (e.g. check `sys.version_info`), but move the version-based hard-fail to early in the entry-point script.

We should do an experiment and try to install tahoe in a py3 virtualenv, and see what happens: I suspect that some of the dependencies (zfec? pycryptopp? foolscap?) will fail to install, so nobody would ever get to the point of even running `tahoe`. If they made it that far, the next question would be whether importing our dependencies would succeed: that might produce different errors depending upon which subcommand was run (since we sometimes avoid importing things before we really need them).
"	defect	closed	normal	1.11.0	packaging	1.10.2	fixed