[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3665: Remove docutils pin from tox configuration

[Tahoe-LAFS]

#3665: Remove docutils pin from tox configuration
------------------------------------+-----------------------
     Reporter:  sajith              |      Owner:  sajith
         Type:  defect              |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by exarkun):

 > If we're pinning anything here, it seems we should pin Sphinx (our
 direct dependency) right?

 I'm not sure.  Sphinx probably doesn't pin its direct dependencies, right?
 The convention seems to be "declare your dependencies unversioned, or
 maybe with an extremely liberal and untested version constraint".  I
 wouldn't expect pinning Sphinx to protect against, eg, docutils
 regressions in a new docutils release.  I would only expect it to protect
 against Sphinx regressions in a new Sphinx release.

 The logical conclusion here is that we should pin *everything* - direct
 and indirect dependencies - not just random dependencies like we do now,
 nor only direct dependencies.  This would protect us against regressions
 in new releases of everything (at least all Python libraries).  It has
 costs too, obviously.  I'm probably willing to put effort into exploring
 this direction.

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