[tahoe-lafs-trac-stream] [tahoe-lafs] #1714: Tahoe-lafs fails to start with python 2.7 due to missing argparse module

[tahoe-lafs]

#1714: Tahoe-lafs fails to start with python 2.7 due to missing argparse module
---------------------------+---------------------------
     Reporter:  vrusinov   |      Owner:  vrusinov
         Type:  defect     |     Status:  new
     Priority:  major      |  Milestone:  undecided
    Component:  packaging  |    Version:  1.9.1
   Resolution:             |   Keywords:  argparse zfec
Launchpad Bug:             |
---------------------------+---------------------------

Comment (by zooko):

 Replying to [comment:6 davidsarah]:
 >
 > Why is that change needed? Just making a new release of zfec as-is would
 solve the problem, no?

 I guess my main reason was that I wanted {{{zfec}}}'s build system to be
 more like {{{Tahoe-LAFS}}}'s. Also, I'm not sure if there could be some
 situation where Python 2.7 is in use, but argparse isn't importable. This
 happened recently, for example, when a Tahoe-LAFS user reported that their
 Python 2.7 didn't have the {{{sqlite}}} module. It wasn't entirely clear
 if this was the *BSD packaging of Python or some custom build of that user
 that had managed to omit this module from the Python standard library.

 In general, I prefer the approach of "try the most specific test that is
 accurate" over "determine the functionality from a version number", when
 practical.

 > (I'm generally -1 on attempting to import modules that are normally only
 runtime dependencies at build time.)

 That's a good consideration, too. In this case I currently prefer the
 above considerations, but I guess I could go either way.

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