[tahoe-lafs-trac-stream] [tahoe-lafs] #393: mutable: implement MDMF

[tahoe-lafs]

#393: mutable: implement MDMF
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  zooko
         Type:           |     Status:  new
  enhancement            |  Milestone:  1.9.0
     Priority:  major    |    Version:  1.0.0
    Component:  code-    |   Keywords:  newcaps performance random-access
  mutable                |  privacy gsoc mdmf mutable backward-
   Resolution:           |  compatibility forward-compatibility review-
Launchpad Bug:           |  needed
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:113 zooko]:
 > Oh, actually there is a unit test failure on the Windows buildslave.

 Fixed in [5147/ticket393-MDMF-2].

 > Looks like a URI in the test is a Python string instead of a Python
 unicode. I guess our caps should always be Python unicode objects, even
 though they don't use non-ASCII characters.

 No, they are UTF-8 {{{str}}} objects (when not decoded into a {{{*URI}}}
 object).

 > I wonder why this happens only on Windows?

 Versions of the {{{simplejson}}} library differ in whether
 {{{simplejson.loads}}} always uses {{{unicode}}} objects, or sometimes
 uses {{{unicode}}} and sometimes {{{str}}} (the latter for strings that
 are representable as ASCII). The version installed on the Windows
 buildslave returns {{{unicode}}} more often. Using
 [source:src/allmydata/util/encodingutil.py at 5073#L125 to_str] on each
 string in the output makes the behaviour consistent. (Note that this isn't
 necessary for keys, only values.)

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/393#comment:114>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage