Yuen Ho Wong <wyue...@gmail.com> added the comment: Yes the charset is irrelevant here. Decoding shouldn't be done here anyway. I think I have to reiterate the problem as accepting unicode strings because it breaks conformance with the WSGI spec. There never should have been unicode strings in the environ in the first place, so never mind transparently handling it without throwing any errors.
As to the problem of using eval(), I can see one can still be paranoid. Perhaps, simply prepending "type ", and a whitespace character like \n as a delimiter will take care of the problem? When you parse on ingress, just split by \n. __________________________________ Repoze Bugs <b...@bugs.repoze.org> <http://bugs.repoze.org/issue101> __________________________________ _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
