Changes between Initial Version and Version 1 of Ticket #1246, comment 5


Ignore:
Timestamp:
2010-11-05T23:24:02Z (14 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1246, comment 5

    initial v1  
    22> I asked freestorm to modify {{{run_trial.py}}} to print out {{{sys.path}}} just before and just after importing {{{pkg_resources}}}. The results show no specific version of the {{{allmydata-tahoe}}} package on either of these paths. In particular, the {{{src}}} directory of the Tahoe-LAFS distribution is not on the "before" path, as I would have expected.
    33
    4 Sorry, I was mistaken. It is on [http://tahoe-lafs.org/trac/tahoe-lafs/attachment/ticket/1246/freestorm-test-with-fake-pkg-output.txt#L24 line 24] "before" and line 68 "after". The reason why the installed Tahoe is being picked up instead is that {{{c:\\python26\\lib\\site-packages}}} is earlier than {{{c:\\buildbot_tahoe_0.8.2\\freestorm_win7-amd64-mingw_py2.6\\build\\src}}} on the "after" path, even though it is later on the "before" path. So importing {{{pkg_resources}}} incorrectly changed the order of these two entries.
     4Sorry, I was mistaken. It is on [http://tahoe-lafs.org/trac/tahoe-lafs/attachment/ticket/1246/freestorm-test-with-fake-pkg-output.txt#L24 line 24] "before" and line 68 "after". The reason why the installed Tahoe is being picked up instead is that {{{c:\python26\lib\site-packages}}} is earlier than {{{c:\buildbot_tahoe_0.8.2\freestorm_win7-amd64-mingw_py2.6\build\src}}} on the "after" path, even though it is later on the "before" path. So importing {{{pkg_resources}}} incorrectly changed the order of these two entries.