[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2747: "tox" on debian (py3) can't run our setup.py

[Tahoe-LAFS]

#2747: "tox" on debian (py3) can't run our setup.py
---------------------------+--------------------
     Reporter:  warner     |      Owner:  warner
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:  1.11.0
    Component:  packaging  |    Version:  1.10.2
   Resolution:             |   Keywords:
Launchpad Bug:             |
---------------------------+--------------------

Comment (by warner):

 I surveyed a couple of releases. All current versions of debian ("sid",
 "testing", and even the latest release "jesse") use a python3-based tox.
 On ubuntu, trusty (14.04LTS) uses py2, but vivid (15.04) and beyond use
 py3. The next Ubuntu LTS (16.04 Xenial) is coming out in a month, and will
 use py3-based tox too.

 We could fix this after 1.11.0 ships, under the theory that most people
 inclined to run unit tests will also be inclined to run from a git
 checkout.

 But if we don't fix this before 1.11.0, most debian/ubuntu users will be
 unable to run the release's unit tests with our recommended process.
 They'll have to create a py2-based virtualenv, `pip install tox` into
 that, then run the resulting executable. Or, since they're going to make a
 virtualenv anyways (to run tahoe), they can just do "trial allmydata" from
 within the virtualenv.

 That doesn't sound like a great experience. It doesn't affect people's
 ability to *use* tahoe, just their ability to run the tests in a standard
 way.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2747#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage