[tahoe-lafs-trac-stream] [tahoe-lafs] #2077: pip packaging plan

[tahoe-lafs]

#2077: pip packaging plan
---------------------------+--------------------------------------
     Reporter:  daira      |      Owner:
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:  undecided
    Component:  packaging  |    Version:  1.10.0
   Resolution:             |   Keywords:  pip packaging setuptools
Launchpad Bug:             |
---------------------------+--------------------------------------

Comment (by daira):

 More on the rationale for parsing {{{requirements.txt}}}:

 We don't want to import our {{{setup.py}}} at run-time because it won't in
 general be installed/built somewhere importable. Therefore, given the
 design criterion of having the requirements specified only in one place,
 the options are either to have {{{setup.py}}} do an {{{execfile}}} on some
 other code file to get the dependencies (as we're doing now), or to have
 both {{{setup.py}}} and {{{allmydata/__init__.py}}} read the requirements
 from the same data file -- which might as well be {{{requirements.txt}}}
 since that has a well-defined existing format.

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