-----BEGIN PGP SIGNED MESSAGE-----
Sidnei da Silva schrieb am 22.06.2006 19:48:
> Looks like Jim added support for pep263 coding to doctest.py at some point.
> However, that doesn't quite play with functional doctests it seems.
> The issue is that functional doctests usually do:
> >>> print http(r"....
> ... and when the response value is printed it's converted to a
> string. But if you set coding in your functional doctest file then the
> expected value is a unicode string. If you have a non-ascii char in
> your response value, *bang*, it bombs with a unicode error.
> Anyone else experienced this?
Yes. I wrote to the User List on 2006-04-16 with the subject: "No
registered publisher found for (GET/)". And I've still the problem.
Egon Frerich, Freudenbergstr. 16, 28213 Bremen
E-Mail: [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v184.108.40.206 (MingW32)
Comment: GnuPT 2.7.2
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope3-dev mailing list