Changes between Initial Version and Version 1 of Ticket #640, comment 4
- Timestamp:
- 2010-11-21T20:19:46Z (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #640, comment 4
initial v1 12 12 > Q2: Can any of the complexity in ./bin/tahoe be removed? 13 13 14 Yes. Most of the complexity is just due to the fact that we have two scripts (this one and {{{ /support/bin/tahoe}}}). The reason why we need two scripts is that the one generated by setuptools doesn't set up the {{{sys.path}}} as we want, and setting the PYTHONPATH environment variable is the documented way to change the initial {{{sys.path}}}. The Windows-specific code is necessary in order to pass on Unicode arguments correctly to the second script, which would not be needed if we only had one script.14 Yes. Most of the complexity is just due to the fact that we have two scripts (this one and {{{support/bin/tahoe}}}). The reason why we need two scripts is that the one generated by setuptools doesn't set up the {{{sys.path}}} as we want, and setting the PYTHONPATH environment variable is the documented way to change the initial {{{sys.path}}}. The Windows-specific code is necessary in order to pass on Unicode arguments correctly to the second script, which would not be needed if we only had one script. 15 15 16 16 > ./support/bin/tahoe is very short and simply calls: load_entry_point('allmydata-tahoe==1.8.0', 'console_scripts', 'tahoe')()