Re: [Zope-dev] Help review #181754
On 2010-7-21 07:32, Wolfgang Schnerring wrote: * Wichert Akkermanwich...@wiggy.net [2010-07-20 19:28]: On 2010-7-20 18:15, Christian Theune wrote: At least, WRT this bug, I don't think it's a good idea to ask explicitly for bad requests to go to the application as the test layer should model real server behaviour as closely as possible. And again it wouldn't make sense anyway as you can't pass an unparsable request to the application. I'm not sure I agree. Like everything else servers have bugs, so it can't hurt to test how your application would behave given certain server bugs. I don't think it is usually a productive assumption that lower layers fail to uphold their end of the contract. Maybe an extrapolation/hyperbole illustrates my opinion: Cosmic rays might also flip bits in your computer's RAM or disk, but I don't think it's worthwile to test how your application reacts when the python interpreter (or whoever, really) presents it with mangled data structures or objects or whatnot. And for some situations you do want to explicitly test for such things. It all depends on how critical your app is. I'm not sure I'm not the only one who has tested code with randomly broken/bit-flipped input to test robustness. Wichert. -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Help review #181754
On 07/21/2010 09:17 AM, Wichert Akkerman wrote: On 2010-7-21 07:32, Wolfgang Schnerring wrote: * Wichert Akkermanwich...@wiggy.net [2010-07-20 19:28]: On 2010-7-20 18:15, Christian Theune wrote: At least, WRT this bug, I don't think it's a good idea to ask explicitly for bad requests to go to the application as the test layer should model real server behaviour as closely as possible. And again it wouldn't make sense anyway as you can't pass an unparsable request to the application. I'm not sure I agree. Like everything else servers have bugs, so it can't hurt to test how your application would behave given certain server bugs. I don't think it is usually a productive assumption that lower layers fail to uphold their end of the contract. Maybe an extrapolation/hyperbole illustrates my opinion: Cosmic rays might also flip bits in your computer's RAM or disk, but I don't think it's worthwile to test how your application reacts when the python interpreter (or whoever, really) presents it with mangled data structures or objects or whatnot. And for some situations you do want to explicitly test for such things. It all depends on how critical your app is. I'm not sure I'm not the only one who has tested code with randomly broken/bit-flipped input to test robustness. That double negative confuses the hell out of me. :) However, I don't think the request of the given bug matches that requirement anyway. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 48 OK, 10 Failed, 1 Unknown
Summary of messages to the zope-tests list. Period Tue Jul 20 12:00:00 2010 UTC to Wed Jul 21 12:00:00 2010 UTC. There were 59 messages: 6 from Zope Tests, 1 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 15 from buildbot at winbot.zope.org, 13 from ccomb at free.fr, 20 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Tue Jul 20 22:04:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017053.html Subject: FAILED : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Tue Jul 20 22:05:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017054.html Subject: FAILED : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Tue Jul 20 22:05:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017055.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Jul 20 22:57:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017062.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Jul 20 23:09:07 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017063.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Tue Jul 20 23:17:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017064.html Subject: FAILED : ZTK 1.0dev / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Wed Jul 21 00:16:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017069.html Subject: FAILED : ZTK 1.0 / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Wed Jul 21 01:52:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017077.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Jul 21 03:28:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017082.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Jul 21 04:23:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017083.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Wed Jul 21 03:01:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017081.html Tests passed OK --- Subject: OK : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:27:00 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017035.html Subject: OK : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:29:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017036.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:29:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017037.html Subject: OK : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:31:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017038.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:32:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017039.html Subject: OK : Zope Buildbot / ztk slave-osx From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:37:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017040.html Subject: OK : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:38:13 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017041.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:39:03 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017042.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:41:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017043.html Subject: OK : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Jul 20 11:46:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017044.html Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Tue Jul 20 21:08:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017045.html Subject: OK : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Tue Jul 20 21:29:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017046.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jul 20 21:32:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017047.html Subject: OK : Zope-2.11
[Zope-dev] zope.hookable ported to Python 3
I've ported zope.hookable too, but I don't need it until it's time to port zope.component (and I think the same goes for zope,security which I think is next if I remember correctly), so I'm not merging the branch yet. It's full if ugly Python 3 hacks, as it's a c-extension. Feel free to take a look and complain if you you like. :-) http://svn.zope.org/zope.hookable/branches/regebro-python3/ -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing / zope.testrunner path forward:
On Wed, Jul 21, 2010 at 06:28, Christian Theune c...@gocept.com wrote: I myself prefer having more releases. I like Marius' idea: 3.10 would be good for removing the test runner then 4.0 can be Py3 compatibility. OK, I'll merge and release 3.10 today or tomorrow or so. -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing / zope.testrunner path forward:
On Tue, Jul 20, 2010 at 23:57, Marius Gedminas mar...@gedmin.as wrote: 1. Should there be BBB imports of zope.testrunner into zope.testing? We can do that to get a longer deprecation period, a couple of months isn't very long). *shrug* Nobody said YES! and since it actually requires that zope.testing depends on zope.testrunner to be pracically useful, I think we'll skip it. -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing / zope.testrunner path forward:
On Wednesday, July 21, 2010, Lennart Regebro wrote: Nobody said YES! and since it actually requires that zope.testing depends on zope.testrunner to be pracically useful, I think we'll skip it. I think nobody cares because everyone uses the test runner recipe. As long as that recipe works, we are good. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing / zope.testrunner path forward:
On Tue, Jul 20, 2010 at 12:32 PM, Lennart Regebro rege...@gmail.com wrote: I'd like to put down some effort this week during the EuroPython sprint to go forward with zope.testing for Python 3. zope.testing 3.9.5 is already deprecating zope.testing.testrunner, but I need to remove it so that I can port zope.testing to Python 3 without going mad. (zope.testrunner runs on Python 3 already, although installing it fails, because it tries to install zope.testing 3.9.5.) The questions are (some have been discussed before, but I don't remember the outcome): My opinions: 1. Should there be BBB imports of zope.testrunner into zope.testing? We can do that to get a longer deprecation period, a couple of months isn't very long). No. 2. Should I release the testrunner-free version before I port to Python 3, or should we do both at once?Doing both at once of course risks more problems than one at a time. On the other hand we might want all changes at once to lessen annoyance. Do whatever is easiest for you. One option would be to release as eggs for Python 3 only. That way, you shouldn't be affecting Python 2 users. 3. It should be zope.testing 4.0.0, right? Yes Jim -- Jim Fulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing / zope.testrunner path forward:
On Wed, Jul 21, 2010 at 15:06, Jim Fulton j...@zope.com wrote: Do whatever is easiest for you. One option would be to release as eggs for Python 3 only. That way, you shouldn't be affecting Python 2 users. I've released 3.10.0 now, and will let that simmer a while. I'm on Europython so please mail me if something breaks so I see it. 4.0.0 is ready, but I'll wait with releasing it for a week at least, I only need it to work on my porting of zc.buildout, and I don't need it uploaded to PyPI. :-) -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] vocabularies missing wihtout zope.app.schema
On Mon, Jan 11, 2010 at 17:52, Hanno Schlichting ha...@hannosch.eu wrote: On Mon, Jan 11, 2010 at 4:31 PM, Roger d...@projekt01.ch wrote: The zope.componentvocabulary package defines some basic vocabulary (factory) classes. Probably we should move the zope/app/schema/vocabulary.py to this package as registry.py. If it doesn't introduce new dependencies, that sounds good. Hi, with the newest plone4 beta there is an empty vocabulary registry because no package imports zope.app.schema any longer. I am not sure if the registry from zope.app.schema belongs to zope.componentvocabulary. After all zope.componentvocabulary provides vocabularies for components while zope.app.schema replaces the current, non component based registry with his own one. How about moving the code into zope.schema and make it the default registry if zope.component is available? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] vocabularies missing wihtout zope.app.schema
On 7/21/10 6:19 PM, Patrick Gerken wrote: On Mon, Jan 11, 2010 at 17:52, Hanno Schlichting ha...@hannosch.eu wrote: On Mon, Jan 11, 2010 at 4:31 PM, Roger d...@projekt01.ch wrote: The zope.componentvocabulary package defines some basic vocabulary (factory) classes. Probably we should move the zope/app/schema/vocabulary.py to this package as registry.py. If it doesn't introduce new dependencies, that sounds good. Hi, with the newest plone4 beta there is an empty vocabulary registry because no package imports zope.app.schema any longer. I am not sure if the registry from zope.app.schema belongs to zope.componentvocabulary. After all zope.componentvocabulary provides vocabularies for components while zope.app.schema replaces the current, non component based registry with his own one. How about moving the code into zope.schema and make it the default registry if zope.component is available? I ran into this yesterday. It is already fixed in lastest Zope 2.12 and Plone trunk (thanks Hanno). The vocab registry that looks up vocabularies as components is now located in Products.Five.schema (to avoid depending on zope.app.schema). For tests it is now initialized in latest Products.PloneTestCase. David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
