[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:  somebody
         Type:  defect     |     Status:  new
     Priority:  major      |  Milestone:  undecided
    Component:  packaging  |    Version:  1.9.1
   Resolution:             |   Keywords:
Launchpad Bug:             |
---------------------------+-----------------------

Comment (by davidsarah):

 It is not setuptools' responsibility to detect the standard library
 version of argparse, or the responsibility of that version to provide pkg-
 info metadata. What is supposed to happen, I believe, is that the argparse
 package is always built (if not installed *as a package*) when building
 dependencies of zfec, and that the version so built
 [https://code.google.com/p/argparse/source/browse/README.txt should work
 fine on Python 2.7]. It is not intended that the standard library version
 be used by zfec (but if it were, as a result of a strangely configured
 sys.path for example, it wouldn't matter because the standard library
 version of argparse is compatible with the package version; and besides
 Tahoe doesn't use the zfec command-line tools).

 vrusinov: how did you install Tahoe? If you installed it from an OS
 package, then that package is broken because it should have declared a
 dependency on the argparse package regardless of whether the OS has Python
 2.7.

 If you installed it using 'python setup.py build', then it should have
 downloaded and built the argparse package, again regardless of whether the
 OS has Python 2.7.

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