[Zope-dev] Zope Tests: 6 OK, 4 Failed
Summary of messages to the zope-tests list. Period Wed Feb 4 12:00:00 2009 UTC to Thu Feb 5 12:00:00 2009 UTC. There were 10 messages: 10 from Zope Tests. Test failures - Subject: FAILED (failures=6) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Wed Feb 4 21:10:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011021.html Subject: FAILED (failures=7) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Feb 4 21:12:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011022.html Subject: FAILED (failures=6) : Zope[2.buildout]-trunk-alltests Python-2.4.5 : Linux From: Zope Tests Date: Wed Feb 4 21:16:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011025.html Subject: FAILED (failures=7) : Zope[2.buildout]-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Feb 4 21:18:14 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011026.html Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Feb 4 21:04:32 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011017.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Wed Feb 4 21:06:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011018.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Wed Feb 4 21:07:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011019.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Wed Feb 4 21:09:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011020.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Wed Feb 4 21:13:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011023.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Feb 4 21:15:13 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011024.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 )
Re: [Zope-dev] Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: Tres Seaver wrote: or grant me the PyPI role needed? http://svn.zope.org/zope.app.zcmlfiles/tags/3.5.3 To return a favor, I just gave you access to zope.app.zcmlfiles. And zope.container plus zope.app.broken as well, just in case ;) I'm fixing dependent packages broken by my changes: could you add me to zope.app.container as well? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com 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 iD8DBQFJiydC+gerLs4ltQ4RAgIFAKCPLG8sOJqc4pFXbuC0335tRUtF1QCgz0Rt b9o7CPZFWXTfQBKQf6N21xY= =FX45 -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 )
Re: [Zope-dev] Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
On Thu, Feb 5, 2009 at 12:52 PM, Tres Seaver tsea...@palladion.com wrote: I'm fixing dependent packages broken by my changes: could you add me to zope.app.container as well? Done. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ 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] dependency cleanup progress report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: Martijn Faassen wrote: Hi there, After a lot of work we have progress to report on the dependency reduction front: http://faassen.n--tree.net/blog/view/weblog/2009/01/29/0 It's been a lot of work to get this far and there's a huge amount of work to be done still, but there is progress! The second dependency graph is against the trunks of all the packages, as we haven't done the releases yet to make this real. We will look into this tomorrow. We also need to document the various procedures we have been using to do this work so that others can jump in and help us. Excellent work! Looking at the zope.container graph: - The zope.publisher dependency is purely there for the 'traverser.py' module, which probably doesn't belong in zope.container at all: it only imports interfaces to set up __adapts__, which suggests that it should be in zope.publisher, or some other package which depends on both (losing the __adapts__ wouldn't be terrible, for instance). - The dependency module pulls in zope.app.dependable: I think it would make more sense to move the event subscriber *into* that package. which would remove the other, indirect dependency on zope.traversing. - The 'testing' module should lose all the zope-specific module-scope imports, even if that means losing some convenience. I have implemented this one by creating a new 'zope.broken' package, and making 'zope.container' and 'zope.app.broken' depend on it: - The 'contained' module has a bunch of dependencies, including a suspicous one on zope.app.broken: if the IBroken check is really needed, then that interface should be moved to another package. and this one: - The zope.exceptions dependency, again from contained, is due to the use of a couple of dubious zope-specific exceptions: o UserError should probably be replaced with the standard ValueError. o DuplicationError should probably be replaced with KeyError. now released in zope.container 3.7.1 and zope.app.container 3.7.1. I also updated the 'zope.app.zcmlfiles' package (now version 3.5.3), which was not including the 'zope.app.broken' package in its dependencies, although it pulls in its ZCML. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com 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 iD8DBQFJiy01+gerLs4ltQ4RAhfHAJ9bhVfaH+Jw/4qEE/c1Yg3ycCl/SQCfbykt InDS4RvBO5qlJ6JPioIhE8I= =pQ0n -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 )
Re: [Zope-dev] Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
Fred Drake wrote: On Thu, Feb 5, 2009 at 12:52 PM, Tres Seaver tsea...@palladion.com wrote: I'm fixing dependent packages broken by my changes: could you add me to zope.app.container as well? Done. Great work in further reducing dependencies Tres! Note that Stephan Richter has a Magic Script that he can run to give you access to all zope.* packages that he has access to. I'm sure he'll do that if you drop him a mail. For newly created packages such as zope.broken, could you make sure it gives owner access to the list of current package owners for other zope.* packages? It's a bit of clicking around to do that as it's quite a list, but it would help people from getting stuck releasing an update in the future. Regards, Martijn ___ 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] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.
Dan Korostelev wrote: Log message for revision 96156: Please, don't just remove things that could be used in users code. Changed: U zope.app.component/trunk/CHANGES.txt U zope.app.component/trunk/src/zope/app/component/metadirectives.py -=- Modified: zope.app.component/trunk/CHANGES.txt === --- zope.app.component/trunk/CHANGES.txt 2009-02-05 18:07:51 UTC (rev 96155) +++ zope.app.component/trunk/CHANGES.txt 2009-02-05 18:22:19 UTC (rev 96156) @@ -5,7 +5,9 @@ 3.6.1 (unreleased) -- -- ... +- Make ``class`` directive schemas importable from old location, + raising a deprecation warning. It was moved in the previous release, + but some custom directives could possibly use its schemas. Out of curiosity, *was* it used by custom directives that you know of? A more philosophical question: are the interfaces used to implement a directive part of a public API that is reusable or not? When we moved the directive implementation I arbitrary made the assumption that it'd be fine to just move them wholesale, but you clearly don't agree. Besides the interfaces, should the implementation also have backwards compatibility imports? I guess sometimes reuse by interface subclassing does happen in directive implementation, but of course we could declare that such reuse is only intra-package. In my mind, it's also less risky to move a directive implementation even if it is reused, as the amount of external reuse is likely rare and is less likely to be in end-user code. The developers of the code layered on top of the directive definition would therefore be quite capable of fixing any breakage quickly. But of course placing a few imports for backwards compatibility is not a lot of work and may be the easiest way out of this set of questions. :) Regards, Martijn ___ 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] Differing case for Buildout on Windows
I've been constantly bitten by a very annoying bug: depending on how you call buildout on Windows, a full rebuild might be triggered, if only the case differs. For example, all the following calls cause buildout to think settings have changed and that things need to be rebuilt. Note only the drive letter changes: c:\Python24\python.exe bin\buildout-script.py -c c:\src\some-project\buildout.cfg c:\Python24\python.exe bin\buildout-script.py -c C:\src\some-project\buildout.cfg C:\Python24\python.exe bin\buildout-script.py -c c:\src\some-project\buildout.cfg C:\Python24\python.exe bin\buildout-script.py -c C:\src\some-project\buildout.cfg Now, I'm wondering what is the best way to fix it. I originally thought of fixing the data as it comes into buildout, but that would cause existing buildouts to all possibly trigger a rebuild. I'm now thinking of fixing the place where buildout detects that the path has been changed as to normalize the path. Thoughts? -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Differing case for Buildout on Windows
On Feb 5, 2009, at 3:36 PM, Sidnei da Silva wrote: I've been constantly bitten by a very annoying bug: depending on how you call buildout on Windows, a full rebuild might be triggered, if only the case differs. For example, all the following calls cause buildout to think settings have changed and that things need to be rebuilt. Note only the drive letter changes: c:\Python24\python.exe bin\buildout-script.py -c c:\src\some-project\buildout.cfg c:\Python24\python.exe bin\buildout-script.py -c C:\src\some-project\buildout.cfg C:\Python24\python.exe bin\buildout-script.py -c c:\src\some-project\buildout.cfg C:\Python24\python.exe bin\buildout-script.py -c C:\src\some-project\buildout.cfg Now, I'm wondering what is the best way to fix it. I originally thought of fixing the data as it comes into buildout, but that would cause existing buildouts to all possibly trigger a rebuild. I'm now thinking of fixing the place where buildout detects that the path has been changed as to normalize the path. Thoughts? I think it would be easiest to have buildout normalize the config path using os.path.normcase where it is input. 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 )
Re: [Zope-dev] Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
2009/2/5 Martijn Faassen faas...@startifact.com: Fred Drake wrote: On Thu, Feb 5, 2009 at 12:52 PM, Tres Seaver tsea...@palladion.com wrote: I'm fixing dependent packages broken by my changes: could you add me to zope.app.container as well? Done. Great work in further reducing dependencies Tres! Note that Stephan Richter has a Magic Script that he can run to give you access to all zope.* packages that he has access to. I'm sure he'll do that if you drop him a mail. For newly created packages such as zope.broken, could you make sure it gives owner access to the list of current package owners for other zope.* packages? It's a bit of clicking around to do that as it's quite a list, but it would help people from getting stuck releasing an update in the future. BTW, it would be great to have that script published so any developer could use it to set roles for new packages. Stephan? :) -- WBR, Dan Korostelev ___ 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] Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
Dan Korostelev wrote: 2009/2/5 Martijn Faassen faas...@startifact.com: Note that Stephan Richter has a Magic Script that he can run to give you access to all zope.* packages that he has access to. I'm sure he'll do that if you drop him a mail. BTW, it would be great to have that script published so any developer could use it to set roles for new packages. Stephan? :) It's called zope.pypisupport and available in SVN ;) Hanno ___ 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] Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: Fred Drake wrote: On Thu, Feb 5, 2009 at 12:52 PM, Tres Seaver tsea...@palladion.com wrote: I'm fixing dependent packages broken by my changes: could you add me to zope.app.container as well? Done. Great work in further reducing dependencies Tres! Note that Stephan Richter has a Magic Script that he can run to give you access to all zope.* packages that he has access to. I'm sure he'll do that if you drop him a mail. For newly created packages such as zope.broken, could you make sure it gives owner access to the list of current package owners for other zope.* packages? It's a bit of clicking around to do that as it's quite a list, but it would help people from getting stuck releasing an update in the future. I'm glad to grant ownership, but I seriously doubt that anybody will ever touch the package. ;) It's whole purpose in life is to hold a single interface, after all. I'm likelier not to forget if somebody who has already done the clicking around kicks in a list of the appropriate IDs (hint, hint...) Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com 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 iD8DBQFJi4AC+gerLs4ltQ4RApzWAKDOe/nw6G5OtI6sUDfTW6ycxdCfiwCeJanD qFv7+15yKUSSJetxu12shfM= =4M76 -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 )
Re: [Zope-dev] Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
On Thursday 05 February 2009, Dan Korostelev wrote: BTW, it would be great to have that script published so any developer could use it to set roles for new packages. Stephan? :) zope.pypisupport Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ 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 )
