Context Navigation

Changes between Initial Version and Version 1 of Ticket #2077, comment 8

initial	v1
1	1	More on the rationale for parsing {{{requirements.txt}}}:
2	2
3		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 ~~dependencie~~s (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.
	3	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 requirements (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.