aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/pythonproxy-utf8_again.mdwn
diff options
context:
space:
mode:
authorchrysn <chrysn@fsfe.org>2014-03-12 11:16:11 +0100
committerchrysn <chrysn@fsfe.org>2014-03-12 11:16:29 +0100
commit3c0e26fe0e9dbde5c60459d6a2a5405b66ad0d44 (patch)
tree7631de8ddcfe7690ff65242114657f6eafb462a7 /doc/bugs/pythonproxy-utf8_again.mdwn
parentc41d47cff0c6a92234ee8694c396e497782cf802 (diff)
downloadikiwiki-3c0e26fe0e9dbde5c60459d6a2a5405b66ad0d44.tar
ikiwiki-3c0e26fe0e9dbde5c60459d6a2a5405b66ad0d44.tar.gz
pythonproxy utf8 trouble again
Diffstat (limited to 'doc/bugs/pythonproxy-utf8_again.mdwn')
-rw-r--r--doc/bugs/pythonproxy-utf8_again.mdwn16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/pythonproxy-utf8_again.mdwn b/doc/bugs/pythonproxy-utf8_again.mdwn
new file mode 100644
index 000000000..96b060003
--- /dev/null
+++ b/doc/bugs/pythonproxy-utf8_again.mdwn
@@ -0,0 +1,16 @@
+[[!template id=gitbranch branch=chrysn/more-proxy-utf8-fail author="[[chrysn]]"]]
+
+the recently introduced fixes for [[crashes in the python proxy even if disabled]]
+caused the typical python2 implicit conversion failures ("'ascii' codec
+can't...") on my debian sid system -- to fix it, i had to revert commit 154c4ea9e.
+
+i did not dig down all the way to the xml / xmlrpc modules, but my impression
+is that some module changed its behavior between stable and sid and now
+generates `unicode` strings instead of `str`.
+
+a [[patch]] to allow both versions by inspecting the types and en-/decoding on
+demand should work both for anarcat's and my case. i did not test the python3
+version, but i'm pretty sure it was already broken after the abovementioned
+patch.
+
+-- [[chrysn]]