[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Sat Nov 3 13:00:00 2007 UTC to Sun Nov 4 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:48:17 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008591.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:49:47 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008592.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:51:17 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008593.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:52:48 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008594.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:54:20 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008595.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. I'll agree -- I don't want the trunk to have *any* version number in it, because I don't want anyone to even think about doing a release from the trunk. It wouldn't need changing, either. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHLcY4+gerLs4ltQ4RAukVAJ9OOGbHUUf5MEN6hia7tKu2y4gdSQCgy1rb e44xwJPeWLzZUtyX2CupBO0= =ReTA -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. I'll agree -- I don't want the trunk to have *any* version number in it, because I don't want anyone to even think about doing a release from the trunk. It wouldn't need changing, either. I'd like that too, but it breaks the expectations you'd have about the development egg that's defined by a trunk checkout. It needs a meaningful version number to satisfy version constraints like z3c.foopkg=1.3. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Checkins] SVN: zope.testbrowser/trunk/ Fix bug introduced in 3.4.1 that created incompatible tracebacks in doctests.
Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Log message for revision 81431: Fix bug introduced in 3.4.1 that created incompatible tracebacks in doctests. This neccesitated adding a patched mechanize to the source tree; patches have been sent to the mechanize project. Yeah, you are right, I changed the errors since the last version of mechanize -- 0.1.7b -- throws the wrong error. I should have used RE normalizers to fix the problem instead of rewriting the doc tests. I will go through the packages that are effected and fix that. I don't think normalizers are necessary. Testbrowser should have never raised different exceptions. Probably the best thing to do would be to put the HTTPErrors back where httperror_seek_wrapper is now. Specifying versions in either the setup.py or buildout.cfg is a really bad idea because it makes it impossible for people with different KGSs to work on packages. I certainly see how putting versions in setup.py is bad, but don't understand how versions in buildout.cfg cause problems. Can you explain? Also, I am not sure that including mechanize in the testbrowser release is a good idea. What if other packages in my repos also use mechanize, but they rely on the good and bad things of the released packages? I think this will end in a big mess. As there's no released version of mechanize that will work, I don't see another option. What alternative do you suggest? (changing cc: to zope-dev) -- Benji York Senior Software Engineer Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
On Nov 3, 2007, at 4:24 PM, Philipp von Weitersehausen wrote: Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. As far as I see (and apparently Jim, too, since he agreed to use this policy) it's the best compromise between - making sure that nobody creates releases from the trunk (hence the dev marker) - giving development eggs from the trunk or a release branch a *meaningful* revision number (hence the version bump you find so silly) Consider this an edict. (Not if I can just remember to add dev) Thanks for putting this together, Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
