[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 vrusinov):

 > Out of curiosity, what operating system is this?

 It's Fedora 16.

 > 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.

 I'm using my own spec to build tahoe-lafs rpm and some additional specs to
 build missing dependencies (including zfec). Specs does nothing more than
 `python setup.py build` and `python setup.py install`.

 It works pefectly on RHEL 5 & 6 (python 2.4 and 2.6), but does not works
 on Fedora 16.

 Of course, I can port python-argparse (which presents on RHEL) to Fedora
 16, but it will look ugly and I'm sure it's not necessary.

 > A simpler solution to this problem is to require Python 2.7! I'm excited
 about Python 2.7
 > because the Python developers have sworn to stop improving the Python 2
 line.

 Yep, but it will break existing installs on all RHEL/CentOS/SL versions
 (not sure about status of 2.7 on other distros), and nobody really want to
 install 2.7 on such distro. Personally I think any wide-used project
 should support at least 2.4. I share you pain as a developer, but as a
 sysadmin I understand the reason why there are lots of users with older
 long-term support systems.

 > My guess is that you installed zfec with Python 2.6 and then upgraded
 your system to
 > Python 2.7.

 No, I did not. I've build zfec 1.4.22 just some days ago. And, oh, Thank
 you! I see you've just released a new version. I will try it.

 > BTW, making a new release of zfec will not help if vrusinov's (or anyone
 else's with the same problem) system is using the OS-packaged zfec. So we
 still need to know how vrusinov installed Tahoe.

 It will help if tahoe-lafs will declare >= zfec-1.4.23 dependency on
 python 2.7. At least it will be clear from error message what needs to be
 upgraded.

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