[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2065: port to Python 3

[Tahoe-LAFS]

#2065: port to Python 3
------------------------+-----------------------
     Reporter:  zooko   |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:  undecided
    Component:  code    |    Version:  1.10.0
   Resolution:          |   Keywords:  Python3
Launchpad Bug:          |
------------------------+-----------------------

Comment (by zooko):

 python-future comes with a automatic (or at least mostly-automatic?)
 converter from Python2 to future: http://python-
 future.org/automatic_conversion.html

 Here's a question for Daira or anyone else to chime in with their opinion:
 suppose we could wave a magic wand and have Tahoe-LAFS completely ported
 to six, nine, or future. Which of those three languages is the best
 programming language? Assume that you will then have to maintain and
 extend Tahoe-LAFS ''in that programming language'' for the next 10 years.

 So the question is: what's the better programming language:
 [https://pypi.python.org/pypi/six six],
 [https://github.com/nandoflorestan/nine nine], or
 [https://pypi.python.org/pypi/future future]?

 (Anyone reading this probably doesn't need to be reminded, but what makes
 a programming language good is that it facilitates auditability and
 testability.)

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