-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote:
Tres Seaver wrote:
I don't know yet -- I planned to look at the failure more closely, and figure out something that would work with the newer mechanize.
Just for your information, what we're doing is using wsgi_intercept, which hooks into zope.testbrowser, which uses mechanize. But I think we actually need more tests for it in zope.app.wsgi.
Anyway, let me know if you need any help on this.
Basically, the new mechanize neither needs nor wants to have the '_http_upgrade_response' key lying around: I fixed the zope.app.wsgi tests by removing it. All the zopeapp tests now pass for me, with that one egg in development mode. If you (or some other Grok developer) can confirm that the zope.app.wsgi trunk still works for your tests, I will release a new version and bump the ZTK config to include it. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkv4I/IACgkQ+gerLs4ltQ6AKQCdGlt1iATNroCCLkyBGmvyxOOq OIsAn2/PCGxe5mg5LsNO2QCG3VekyGxB =7U+v -----END PGP SIGNATURE-----