[tahoe-dev] [tahoe-lafs] #329: dirnodes could cache encrypted/serialized entries for speed

[tahoe-lafs]

#329: dirnodes could cache encrypted/serialized entries for speed
---------------------------+------------------------------------------------
 Reporter:  warner         |           Owner:  kevan    
     Type:  enhancement    |          Status:  new      
 Priority:  minor          |       Milestone:  undecided
Component:  code-dirnodes  |         Version:  0.8.0    
 Keywords:  dirnode        |   Launchpad_bug:           
---------------------------+------------------------------------------------

Comment(by kevan):

 I've started work on the first point by writing a little program to try to
 get the base32 representation of the output of _pack_contents.
 Unfortunately, I run into path issues when I try to run it.

 At the top of my script, I have

 {{{
 import sys

 base = "/path-to-tahoe/tahoe/support/lib/python2.6/site-packages"
 sys.path.append(base)
 }}}

 to tell the Python interpreter about tahoe's support directory. The goal
 was to have a somewhat less robust version of the detection that the tahoe
 executable does when it first starts (since I know where the directory is
 on my system, and don't imagine that the script is going to be run
 elsewhere, since it's kind of a one-time deal to make tests work).

 When I run the script, and try to import something from the tests
 directory, I get

 {{{
 Traceback (most recent call last):
   File "get_dirnode_strings.py", line 7, in <module>
     from test.test_dirnode import FakeClient
   File "/path-to-tahoe/tahoe/src/allmydata/test/__init__.py", line 2, in
 <module>
     from foolscap.logging.incident import IncidentQualifier
 ImportError: No module named foolscap.logging.incident
 }}}

 which would seem to suggest that my path hacking doesn't do what I want it
 to.

 Is there something easy that I'm missing that would make this work?

 (also, my approach for getting this information is based on what of
 tahoe's code I've read, which isn't much. if there's a more obvious way to
 get the strings that we need, or if my program is flawed in some other
 way, please let me know)

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/329#comment:7>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid