py3kcompat: added a "compatibility layer" for py3k
This patch adds some ugly constructs. The first of them is bytesformatter, a
function that formats strings like when '%' is called. The main motivation for
this function is py3k's strange behavior:
>>> 'foo %s' % b'bar'
"foo b'bar'"
>>> b'foo %s' % b'bar'
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: unsupported operand type(s) for %: 'bytes' and 'bytes'
>>> b'foo %s' % 'bar'
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: unsupported operand type(s) for %: 'bytes' and 'str'
In other words, if we can't format bytes with bytes, and recall that all
mercurial strings will be converted by a fixer, then things will break badly if
we don't take a similar approach.
The other addition with this patch is that the os.environ dictionary is
monkeypatched to have bytes items. Hopefully this won't be needed in the
future, as python 3.2 might get a os.environb dictionary that holds bytes
items.
#!/bin/sh
# http://mercurial.selenic.com/bts/issue322
echo % file replaced with directory
hg init a
cd a
echo a > a
hg commit -Ama
rm a
mkdir a
echo a > a/a
echo % should fail - would corrupt dirstate
hg add a/a
cd ..
echo % directory replaced with file
hg init c
cd c
mkdir a
echo a > a/a
hg commit -Ama
rm -r a
echo a > a
echo % should fail - would corrupt dirstate
hg add a
cd ..
echo % directory replaced with file
hg init d
cd d
mkdir b
mkdir b/c
echo a > b/c/d
hg commit -Ama
rm -r b
echo a > b
echo % should fail - would corrupt dirstate
hg add b
exit 0