Re: [Zope3-dev] Displaying ReStructered Text
Hi, have a look at the rest2html function in http://svn.zope.org/*checkout*/zope3org/trunk/src/zorg/restsupport/__init__.py?content-type=text which uses the zope.app.renderer.rest module. Regards, Uwe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] doctest, functional doctests and pep263 encoding
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? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] doctest, functional doctests and pep263 encoding
Warning: This comment is totally OT from your actual question, sorry. Sidnei da Silva wrote: The issue is that functional doctests usually do: print http(r Most people prefer zope.testbrowser functional tests over old-style functional tests (when applicable), so I'm curious as to why you're using them here. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] doctest, functional doctests and pep263 encoding
Sidnei da Silva wrote: On Thu, Jun 22, 2006 at 02:50:42PM -0400, Benji York wrote: | Warning: This comment is totally OT from your actual question, sorry. | | Sidnei da Silva wrote: | The issue is that functional doctests usually do: | |print http(r | | Most people prefer zope.testbrowser functional tests over old-style | functional tests (when applicable), so I'm curious as to why you're | using them here. It's an old test written almost 2 years ago that started failing in Zope 2.9 due to the changes and the inclusion of a newer zope.testing. I figured something like that. Thanks for satisfying my idle curiosity. :) -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] doctest, functional doctests and pep263 encoding
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 v1.4.2.2 (MingW32) Comment: GnuPT 2.7.2 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEmw+buTzybIiyjvURAsFRAJ9Pln8vHIg8fPzWrQYDVBGDBKXDDgCffzFB ltbSlG4LUxPDvwbxXp2DLkE= =nJAE -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
