tahoe-lafs/tahoe-lafs
tahoe-lafs
/
tahoe-lafs
2
0
Fork 0
Code Issues Pull Requests 23 Packages Projects Releases 1 Wiki Activity

mutable: remove work-around for a flaw in an older version of foolscap 

We now require "foolscap[secure_connections] >= 0.3.0", per [source:_auto_deps.py].
This commit is contained in:
Zooko O'Whielacronx 2008-08-26 08:50:55 -07:00
parent f94c9b58ab
commit f7b4c45d46
1 changed files with 1 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
src/allmydata/mutable/publish.py
View File

@ -576,18 +576,7 @@ class Publish:
else:
# add a testv that requires the share not exist
#testv = (0, 1, 'eq', "")
# Unfortunately, foolscap-0.2.5 has a bug in the way inbound
# constraints are handled. If the same object is referenced
# multiple times inside the arguments, foolscap emits a
# 'reference' token instead of a distinct copy of the
# argument. The bug is that these 'reference' tokens are not
# accepted by the inbound constraint code. To work around
# this, we need to prevent python from interning the
# (constant) tuple, by creating a new copy of this vector
# each time. This bug is fixed in later versions of foolscap.
testv = tuple([0, 1, 'eq', ""])
testv = (0, 1, 'eq', "")
testvs = [testv]
# the write vector is simply the share