[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Thu Mar 20 12:00:00 2008 UTC to Fri Mar 21 12:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu Mar 20 21:53:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-March/009280.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Mar 20 21:55:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-March/009281.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Mar 20 21:56:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-March/009282.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Mar 20 21:58:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-March/009283.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Mar 20 21:59:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-March/009284.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] Reducing dependencies of zope.publisher
I'd like reduce the barrier of entry for using the Zope 3 zope publisher. Right now, it has quite a few dependencies setuptools, zope.component, zope.event, zope.exceptions, zope.i18n, zope.interface, zope.location, zope.proxy, zope.security, zope.deprecation, and zope.deferredimport. This seems a bit extreme. I can get rid of zope.deprecation and zope.deferredimport directly. I'd like to get rid of more. I'm thinking of creating a separate package that contains much of the guts of zope.publisher, but without most or all of the existing dependencies. I'd then modify zope.publisher to import code from this other package, adding the bits that exist now that cause the dependencies. This new package would a number of things, including skin support, xmlrpc support, mapply, interface declarations and various view base classes that now live in zope.publisher. Thoughts? Objections? 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] Reducing dependencies of zope.publisher
Jim Fulton wrote: This new package would a number of things [...] This new package would do what to a number of things? -- 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] Reducing dependencies of zope.publisher
On Mar 21, 2008, at 11:09 AM, Benji York wrote: Jim Fulton wrote: This new package would a number of things [...] This new package would do what to a number of things? Gaaah. Sorry. It would omit them. :) 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] Reducing dependencies of zope.publisher
Hi Jim. What does this mean? Will the new package be a drop in replacement for what we have without some direction on what to do with the other bit or will it break our applications. A working publisher is pretty essential to a functioning zope app. Does this mean the end of deprecation warnings for the publisher? Is this not useful? Many thanks. Regards, David Jim Fulton wrote: I'd like reduce the barrier of entry for using the Zope 3 zope publisher. Right now, it has quite a few dependencies setuptools, zope.component, zope.event, zope.exceptions, zope.i18n, zope.interface, zope.location, zope.proxy, zope.security, zope.deprecation, and zope.deferredimport. This seems a bit extreme. I can get rid of zope.deprecation and zope.deferredimport directly. I'd like to get rid of more. I'm thinking of creating a separate package that contains much of the guts of zope.publisher, but without most or all of the existing dependencies. I'd then modify zope.publisher to import code from this other package, adding the bits that exist now that cause the dependencies. This new package would a number of things, including skin support, xmlrpc support, mapply, interface declarations and various view base classes that now live in zope.publisher. Thoughts? Objections? 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 ) ___ 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] Reducing dependencies of zope.publisher
On Fri, Mar 21, 2008 at 3:46 PM, Jim Fulton [EMAIL PROTECTED] wrote: Thoughts? Objections? I've caught the repoze bug, and if this makes a Repoze.zope3 easier to do/happier, then I'm all for it. In fact, I wouldn't mind if repoze became the official zope3 story. It would definitely help towards the goal of making Zope2 a Zope3 product. :) -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ 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] Reducing dependencies of zope.publisher
On Mar 21, 2008, at 12:10 PM, David Pratt wrote: Hi Jim. What does this mean? It wouldn't have any visible effect on zope.publisher. Applications that use zope.publisher wouldn't see a change. There would be an alternative to zope.publisher that has far fewer dependencies and fewer features. zope.publisher would build on this lower-level thing. The low-level package would be well suited to people who want to build small web applications with Python. As people have more requirements, they might graduate from the smaller framework to zope.publisher. 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] Reducing dependencies of zope.publisher
On Mar 21, 2008, at 12:55 PM, Jim Fulton wrote: On Mar 21, 2008, at 12:15 PM, Lennart Regebro wrote: On Fri, Mar 21, 2008 at 3:46 PM, Jim Fulton [EMAIL PROTECTED] wrote: Thoughts? Objections? I've caught the repoze bug, and if this makes a Repoze.zope3 easier to do/happier, then I'm all for it. I suspect the work I did a couple of weeks ago adding paste support to zope.publisher would go a long way. That was released in zope.publisher 3.5.0. Then again, since this makes it easy to use zope3 in paste, I don't know what repose adds. 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 )
Nitpicking about coding standards (was Re: [Zope-dev] zope.sendmail grantma-retryfixes branch review)
On Thu, Mar 20, 2008 at 10:33:10PM +, Chris Withers wrote: Marius Gedminas wrote: +Process results of an SMTP error + returns True to indicate break needed The standard docstring convention is to do this: Process results of an SMTP error. There was a blank line here that you omitted. Returns True to indicate break needed. This standard sucks. Process results of an SMTP error. Returns True to indicate break needed. ...is much more readable. If there's a tool that does something silly with this, fix the tool. It's a matter of taste, perhaps, because I do find Short sentence. Longer description. nicer than your example. Luckily, PEP-8 agrees with my taste. :-) Okay, I lied. PEP-8 says to add an extra blank line before the closing (because Emacs' paragraph wrapping command sucks), and thus you get this: Short sentence. Longer description. but I don't recall ever seeing this variant in the Zope 3 tree. I completely agree with your sentiment (fix the damn tool!) here. My beloved vim can format the longer description without touching the trailing . Also, it's conventional to leave two blank lines between class and interface declarations. (PEP-8 says this.) What does this actually mean? I couldn't follow from your example. I'll try to give a better example. Count the blank lines in it: class OneClass(object): Docstring. def a_method(self): Docstring. code code code def b_method(self): Docstring. code code class AnotherClass(object): Docstring. def a_method(self): Docstring. code code class ThirdClass(object): Docstring. - Class definitions are separated by two blank lines. Method definitions are separated by a single blank line. That's what PEP-8 says. Other than that, completely agree with everything you said :-) It's always the little and unimportant things that get the most attention and discussion. On the other hand, at least we have a consensus (PEP-8) in the Python community, unlike those poor C++ brace style flame war veterans. I suppose having no braces helps ;-) Cheers! Marius Gedminas -- The day after tomorrow is the third day of the rest of your life. signature.asc Description: Digital 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] Packaging Zope for Fedora
As the subject implies, I'm working on a package for Fedora. I've come across some missing dependencies, and some that are different versions. Because of the way that Python packages are put together (shared library environment), I'm trying to strip out everything that is not Zope specific (e.g. mechanize, docutils, etc.) that way Zope won't clobber already existing packages, and new packages won't clobber Zope. Here is my list (that I've discovered so far...) and some notes and questions. I would appreciate any information on resolving these. My list was taken from Zope-3.4.0c1/build/lib.linux-x86_64-2.5 (in my arch specific case...) after doing a `python install.py build` (side note, why is it called install.py and not setup.py?). BTrees -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? ClientForm -- This currently exists in Fedora (version 0.2.7) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? twisted -- This currently exists in Fedora (version 2.4.0) Diffing the directories reveals that is it mostly compatible, however, missing some features (I have a list). What parts are required by Zope? Some of the missing parts are no longer being maintained, or are incompatible with newest Twisted (2.5.0). Thoughts? mechanize -- This currently exists in Fedora (version 0.1.6) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? persistent -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? pytz -- This currently exists in Fedora (version 2006p) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? The Zope versions do not have the .py extension. Possible problems with Zope if they do (i.e., lib resolving)? RestrictedPython -- Does not currently exist in Fedora as a separate package. Is this it? http://pypi.python.org/pypi/RestrictedPython/3.4.2 Required version for Zope? What about newer versions? ThreadedAsync -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? transaction -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If not Zope origin, is it useful outside of Zope? Also, there is an existing package in Fedora called python-zope-interface, version 3.0.1 I assume (in F8), and I'm wondering if it would be worth keeping separate (or at least available, updated, maybe with a Conflicts: zope) in Fedora and are there other parts of Zope (e.g. ZODB, ZEO) that would be useful by themselves? I'm sorry if this seems daunting (it is on my side ;) and/or demanding, but I would like this packaged the best possible way for both projects. Who knows, this might show up in future RHEL versions (maybe I'm delusional ;) Thank you for your time and patience. --Tim _ / According to Kentucky state law, every person must take a bath at least \ \ once a year./ - \ \ \ \ /\ ( ) .( o ). ___ 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] Packaging Zope for Fedora
Hi, speaking as the Zope 2 release manager: I am strongly opposed against splitting Zope yourself into different packages and modules. With Zope 2 depending from various Zope 3 packages (roughly 80-90) we have already the situation to keep track which packages belong together. This will become even more complicated when each Zope 3 package will have its own life-cycle. I doubt that you as a package can keep track in a reliable way with those requirements. It is somewhat hard for me to follow. So why can't you leave the Zope source packages as they are? Splitting up Zope into even more packages is even more error-prone. Re-packaged Zope distributions always raised more problems in the past than they really solved. The deployment for Zope-based applications is nowadays based on zc.buildout. Serious solutions providers never go with distribution-specific packages. Andreas --On 21. März 2008 11:57:31 -0700 Timothy Selivanow [EMAIL PROTECTED] wrote: As the subject implies, I'm working on a package for Fedora. I've come across some missing dependencies, and some that are different versions. Because of the way that Python packages are put together (shared library environment), I'm trying to strip out everything that is not Zope specific (e.g. mechanize, docutils, etc.) that way Zope won't clobber already existing packages, and new packages won't clobber Zope. Here is my list (that I've discovered so far...) and some notes and questions. I would appreciate any information on resolving these. My list was taken from Zope-3.4.0c1/build/lib.linux-x86_64-2.5 (in my arch specific case...) after doing a `python install.py build` (side note, why is it called install.py and not setup.py?). BTrees -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? ClientForm -- This currently exists in Fedora (version 0.2.7) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? twisted -- This currently exists in Fedora (version 2.4.0) Diffing the directories reveals that is it mostly compatible, however, missing some features (I have a list). What parts are required by Zope? Some of the missing parts are no longer being maintained, or are incompatible with newest Twisted (2.5.0). Thoughts? mechanize -- This currently exists in Fedora (version 0.1.6) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? persistent -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? pytz -- This currently exists in Fedora (version 2006p) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? The Zope versions do not have the .py extension. Possible problems with Zope if they do (i.e., lib resolving)? RestrictedPython -- Does not currently exist in Fedora as a separate package. Is this it? http://pypi.python.org/pypi/RestrictedPython/3.4.2 Required version for Zope? What about newer versions? ThreadedAsync -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? transaction -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If not Zope origin, is it useful outside of Zope? Also, there is an existing package in Fedora called python-zope-interface, version 3.0.1 I assume (in F8), and I'm wondering if it would be worth keeping separate (or at least available, updated, maybe with a Conflicts: zope) in Fedora and are there other parts of Zope (e.g. ZODB, ZEO) that would be useful by themselves? I'm sorry if this seems daunting (it is on my side ;) and/or demanding, but I would like this packaged the best possible way for both projects. Who knows, this might show up in future RHEL versions (maybe I'm delusional ;) Thank you for your time and patience. --Tim _ / According to Kentucky state law, every person must take a bath at least \ \ once a year. / -\ \ \ \ /\ ( ) .( o ). ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists -
[Zope-dev] Re: Reducing dependencies of zope.publisher
Jim Fulton wrote: On Mar 21, 2008, at 12:55 PM, Jim Fulton wrote: On Mar 21, 2008, at 12:15 PM, Lennart Regebro wrote: On Fri, Mar 21, 2008 at 3:46 PM, Jim Fulton [EMAIL PROTECTED] wrote: Thoughts? Objections? I've caught the repoze bug, and if this makes a Repoze.zope3 easier to do/happier, then I'm all for it. I suspect the work I did a couple of weeks ago adding paste support to zope.publisher would go a long way. That was released in zope.publisher 3.5.0. Then again, since this makes it easy to use zope3 in paste, I don't know what repose adds. It splits virtual hosting, transaction management, error logging and retry out as WSGI middleware. I'm not sure how much of that is shared between Zope 2 and Zope 3, of course. Really, I see Repoze as being mainly about patterns and packaging. I'm sure Chris and Tres would like to maintain as little software as possible. One thing that sucks right now for the repoze.zope2 story is that Zope 2 isn't officially packaged in an egg-friendly form so the Repoze guys have to repackage it. It'd be great to be able to get Zope 2 released in a way that can at least optionally be installable as eggs. Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ 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: Reducing dependencies of zope.publisher
--On 21. März 2008 19:20:46 + Martin Aspeli [EMAIL PROTECTED] wrote: One thing that sucks right now for the repoze.zope2 story is that Zope 2 isn't officially packaged in an egg-friendly form so the Repoze guys have to repackage it. It'd be great to be able to get Zope 2 released in a way that can at least optionally be installable as eggs. I think this should be a major goal for Zope 2.12. We possibly will have a Zope-(2 oriented) sprint in summer in Germany. If there are volunteers and interest I could add this to the possible sprint topics. Feedback welcome. Andreas pgpgRkQooVauX.pgp Description: 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: Reducing dependencies of zope.publisher
Andreas Jung wrote: --On 21. März 2008 19:20:46 + Martin Aspeli [EMAIL PROTECTED] wrote: One thing that sucks right now for the repoze.zope2 story is that Zope 2 isn't officially packaged in an egg-friendly form so the Repoze guys have to repackage it. It'd be great to be able to get Zope 2 released in a way that can at least optionally be installable as eggs. I think this should be a major goal for Zope 2.12. We possibly will have a Zope-(2 oriented) sprint in summer in Germany. If there are volunteers and interest I could add this to the possible sprint topics. Feedback welcome. Awesome! Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ 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] Packaging Zope for Fedora
On Fri, 2008-03-21 at 20:09 +0100, Andreas Jung wrote: Hi, speaking as the Zope 2 release manager: I am strongly opposed against splitting Zope yourself into different packages and modules. With Zope 2 depending from various Zope 3 packages (roughly 80-90) we have already the situation to keep track which packages belong together. My concern is more with striping out the non-Zope pieces. If there are pieces of Zope that are useful outside of Zope (e.g. in some other project, or someones personal code...) I thought it would be nice to offer those as a separate piece so that someone could use just that piece. Having 80-90 different RPMs _would_ be rather unmaintainable. I'd only pull out the first few useful ones, and then others by-demand. My biggest concern is removing the non-Zope parts. As far as Zope2 is concerned, I'll cross that bridge later. Newest technology is /generally/ the focus of Fedora. This will become even more complicated when each Zope 3 package will have its own life-cycle. I doubt that you as a package can keep track in a reliable way with those requirements. It is somewhat hard for me to follow. The Eclipse project has done an awesome job, and so has Fedora in keeping up with it (they actually work very closely together). I'm not concerned with ripping Zope /completely/ apart, but rather I thought /some/ parts might be useful by themselves, like the ZODB for example. So why can't you leave the Zope source packages as they are? Splitting up Zope into even more packages is even more error-prone. Re-packaged Zope distributions always raised more problems in the past than they really solved. The deployment for Zope-based applications is nowadays based on zc.buildout. So, are you saying that you would rather Zope not be in Fedora, or any other distro, and just leave it up to the user? Serious solutions providers never go with distribution-specific packages. Some do, but that's not the focus of me packaging Zope. Since Fedora's focus is not for production (yes, people do use Fedora in production, e.g. NASA, but that is their onus), but rather development and blazing new trails. This would provide more code and utilities for people to use and experiment with. --Tim __ / As of next Tuesday, C will be flushed in favor of COBOL. \ \ Please update your programs. / -- \ \ \ \ /\ ( ) .( o ). ___ 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] zope.interface compatibility question
I hope this is the right list for my question related to zope.interface: I use some (non-zope) software which uses zope.interface (currently 3.0.1). Now there is another software which needs a newer version of zope.interface. Is the zope.interface library (3.4) backwards compatible with 3.0.1? Can I expect that the old software will still work if I install the new library? Thank you very much, sorry for bothering. fs smime.p7s Description: S/MIME Cryptographic 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] Reducing dependencies of zope.publisher
Hi Jim. OK great. Many thanks for elaborating. This will be progressive. I had been considering an application use case without a zodb. Is this the scenario that the basic publisher would facilitate? Regards, David Jim Fulton wrote: On Mar 21, 2008, at 12:10 PM, David Pratt wrote: Hi Jim. What does this mean? It wouldn't have any visible effect on zope.publisher. Applications that use zope.publisher wouldn't see a change. There would be an alternative to zope.publisher that has far fewer dependencies and fewer features. zope.publisher would build on this lower-level thing. The low-level package would be well suited to people who want to build small web applications with Python. As people have more requirements, they might graduate from the smaller framework to zope.publisher. 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] Packaging Zope for Fedora
Disclaimer: my knowledge is not complete, and my track record of writing emails late at night is not very good. Take this with a big grain of salt. On Fri, Mar 21, 2008 at 11:57:31AM -0700, Timothy Selivanow wrote: As the subject implies, I'm working on a package for Fedora. I've come across some missing dependencies, and some that are different versions. Because of the way that Python packages are put together (shared library environment), I'm trying to strip out everything that is not Zope specific (e.g. mechanize, docutils, etc.) that way Zope won't clobber already existing packages, and new packages won't clobber Zope. Be careful: I wouldn't be surprised if the foreign packages in the Zope tree have bugfixes applied to them. I trust those fixes were also sent to their respective upstreams as well, but it may make it a bit more difficult to find out which upstream version is really needed. Here is my list (that I've discovered so far...) and some notes and questions. I would appreciate any information on resolving these. My list was taken from Zope-3.4.0c1/build/lib.linux-x86_64-2.5 (in my arch specific case...) after doing a `python install.py build` (side note, why is it called install.py and not setup.py?). Good question. It's called setup.py in the Subversion tree -- but the tarball is not based on the old monolithic SVN tree any more. BTrees -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? It is part of ZODB. It may be useful outside of Zope. persistent -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? ZODB again. transaction -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If not Zope origin, is it useful outside of Zope? ZODB again. ThreadedAsync -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? ZODB again. ClientForm -- This currently exists in Fedora (version 0.2.7) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? mechanize -- This currently exists in Fedora (version 0.1.6) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? I'm pretty sure these two are only used for zope.testbrowser. It ought to be sufficient to take the latest upstream version and see if zope.testbrowser's test suite passes with it. Benji York is the one with most knowledge about zope.testbrowser and its dependencies. If he offers different advice, listen to him, not to me. twisted -- This currently exists in Fedora (version 2.4.0) Diffing the directories reveals that is it mostly compatible, however, missing some features (I have a list). What parts are required by Zope? Some of the missing parts are no longer being maintained, or are incompatible with newest Twisted (2.5.0). Thoughts? AFAIK twisted is only bundled with Zope 3 for convenience. It is used for its HTTP server as one of the alternatives (the other ones being ZServer and WSGI), but even that part is not used by default. pytz -- This currently exists in Fedora (version 2006p) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? The Zope versions do not have the .py extension. Possible problems with Zope if they do (i.e., lib resolving)? I think any non-broken pytz version should work. (Ubuntu once shipped a completely broken one.) RestrictedPython -- Does not currently exist in Fedora as a separate package. Is this it? http://pypi.python.org/pypi/RestrictedPython/3.4.2 Required version for Zope? What about newer versions? I honestly have no idea. Also, there is an existing package in Fedora called python-zope-interface, version 3.0.1 I assume (in F8), and I'm wondering if it would be worth keeping separate (or at least available, updated, maybe with a Conflicts: zope) in Fedora and are there other parts of Zope (e.g. ZODB, ZEO) that would be useful by themselves? Yes and no. The Zope 3 upstream is now split into hundreds of little packages (Python eggs), each registered on the Python Package Index, with intricate and sometimes suboptimal dependency lists. If there's an easy way to convert a Python egg to an RPM, you may want to look at this, but beware: the dust hasn't fully settled yet. There's no guarantee that the packages on PyPI will work
[Zope-dev] Re: Packaging Zope for Fedora
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Gedminas wrote: Disclaimer: my knowledge is not complete, and my track record of writing emails late at night is not very good. Take this with a big grain of salt. On Fri, Mar 21, 2008 at 11:57:31AM -0700, Timothy Selivanow wrote: As the subject implies, I'm working on a package for Fedora. I've come across some missing dependencies, and some that are different versions. Because of the way that Python packages are put together (shared library environment), I'm trying to strip out everything that is not Zope specific (e.g. mechanize, docutils, etc.) that way Zope won't clobber already existing packages, and new packages won't clobber Zope. I would also emphasize (maybe the OP knows this) that it isn't going to be sensible to rely on the Zope3 packages as canonical for packaging Zope: Zope3 is not an upgrade / replacement for Zope2. In particular, Zope2 depends on a specific subset of the Zope3 packages, but also includes a bunch of other packages. The OP might find the following source distributions instructive: - http://dist.repoze.org/zopelib-2.10.5.0.tar.gz contains the Zope2 packages plus the relevant Zope3 code, drawn from Zope 3.3.2. It also includes most of the foreign packages the OP identified, except those in the ZODB egg. - http://dist.repoze.org/ZODB3-3.7.2.tar.gz contains the ZODB packages, including transaction and ThreadedAsync. This is the version that the zopelib distribution depends on. Be careful: I wouldn't be surprised if the foreign packages in the Zope tree have bugfixes applied to them. I trust those fixes were also sent to their respective upstreams as well, but it may make it a bit more difficult to find out which upstream version is really needed. Here is my list (that I've discovered so far...) and some notes and questions. I would appreciate any information on resolving these. My list was taken from Zope-3.4.0c1/build/lib.linux-x86_64-2.5 (in my arch specific case...) after doing a `python install.py build` (side note, why is it called install.py and not setup.py?). Good question. It's called setup.py in the Subversion tree -- but the tarball is not based on the old monolithic SVN tree any more. The Zope3 tarball is already EOLed (there won't be a 3.5 version released as a monolithic tarball, AFAIK). The Zope2 tarball will undergo one final release series (2.11.x), with plans / discussion / work underway to decompose it as eggs for the 2.12 release. BTrees -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? It is part of ZODB. It may be useful outside of Zope. persistent -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? ZODB again. transaction -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If not Zope origin, is it useful outside of Zope? ZODB again. Now split out from th ZODB trunk (maybe not released as such yet). ThreadedAsync -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? ZODB again. Gone in the ZODB trunk (again, maybe not yet released). ClientForm -- This currently exists in Fedora (version 0.2.7) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? mechanize -- This currently exists in Fedora (version 0.1.6) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? I'm pretty sure these two are only used for zope.testbrowser. It ought to be sufficient to take the latest upstream version and see if zope.testbrowser's test suite passes with it. Benji York is the one with most knowledge about zope.testbrowser and its dependencies. If he offers different advice, listen to him, not to me. twisted -- This currently exists in Fedora (version 2.4.0) Diffing the directories reveals that is it mostly compatible, however, missing some features (I have a list). What parts are required by Zope? Some of the missing parts are no longer being maintained, or are incompatible with newest Twisted (2.5.0). Thoughts? AFAIK twisted is only bundled with Zope 3 for convenience. It is used for its HTTP server as one of the alternatives (the other ones being ZServer and WSGI), but even that part is not used by default. pytz -- This currently exists in Fedora (version 2006p) Diffing the directories and files reveals
Re: [Zope] Questions about the installer, packaging
--On 20. März 2008 16:32:45 -0700 Timothy Selivanow [EMAIL PROTECTED] wrote: I'm investigating the creation of an RPM for Fedora, but I'd like to get some info before I dive too deeply... 1) It seems like the packaging list is defunct, or at least hasn't had anything but SPAM since 2003. Is there an appropriate list to discuss packaging issues (zope-dev perhaps)? zope-dev. The source code release is just a tar archive of the source tree which is sufficient for building Zope. 2) Is there any documentation on the installer options to help with placing things in the correct distro specific directories? The Zope distributions (except for Windows) don't care about distro-specific needs (and never will). Andreas pgp9KIS34OMF2.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Simple security question
http://plone.org/documentation/how-to/debug-unauthorized -aj --On 21. März 2008 08:38:46 -0400 Duncan Murdoch [EMAIL PROTECTED] wrote: I'm making some changes to an existing Zope setup. The original author has moved on, and I don't have previous experience with Zope: so the setup is relatively well-designed, but I don't really know the low-level basics well. It's some version of Zope 2 (I'm not sure how to get exact version information.) The problem is this: we have an existing web site that works well. I'd like to create a few pages that are private, accessible only by a list of authorized users. So I created a new directory, and added some users to the acl_users folder. Then on the security page for this directory, I unchecked all the acquire permission settings boxes, and checked every permission for the class of user I created. (Later I'll reduce the list, but for now they have everything.) But they still get permission failures when they try to do anything. The log shows the error: You are not allowed to access 'pythonMethods' in this context I have several directories with that name on different parts of the site, so it's not completely clear to me which one I'm not allowed to access. The error log shows this traceback: Traceback (innermost last): * Module ZPublisher.Publish, line 98, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 39, in call_object * Module OFS.DTMLDocument, line 133, in __call__ DTMLDocument instance at bfa00e0 URL: http://xxx/test/edit/manage_main Physical Path:/xxx/test/edit * Module DocumentTemplate.DT_String, line 474, in __call__ * Module DocumentTemplate.DT_Util, line 195, in eval __traceback_info__: pythonMethods * Module OFS.DTMLMethod, line 152, in validate Unauthorized: You are not allowed to access 'pythonMethods' in this context (I've xx'd out the URL because I'm pretty sure I haven't got the security setup right.) The test/edit page is a DTML document, which contains this line dtml-var pythonMethods.displayheader(id()) but I'm not certain this is the line that triggers the error. My questions: 1. Are there simple examples of this kind of security setup somewhere? 2. How do I diagnose what's going wrong? Duncan Murdoch ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting pgpFNk8b33ivB.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Questions about the installer, packaging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timothy Selivanow wrote: I'm investigating the creation of an RPM for Fedora, but I'd like to get some info before I dive too deeply... 1) It seems like the packaging list is defunct, or at least hasn't had anything but SPAM since 2003. Is there an appropriate list to discuss packaging issues (zope-dev perhaps)? 2) Is there any documentation on the installer options to help with placing things in the correct distro specific directories? Under the covers, the Zope makefile is using the distutils infrastructure, via its 'setup.py' script. You can see the arguments used by the two commands via:: $ /path/to/python setup.py build --help and:: $ /path/to/python setup.py install --help 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 iD8DBQFH48aq+gerLs4ltQ4RAqMJAJ9dat4tsfU760puNxnuazoiX1yQ/ACfcHJR aej1z6rahMyOMxw68eQsK0I= =iUU8 -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope utf-8 problem using MySQL
Hugo Ramos wrote at 2008-3-19 18:11 +: ... The problem is that when retrieving data from a table the international chars become alien symbols... How do you retrieve the data? You should check the data immediately when you receive it from the database. If it is already wrong at this place, you know there is a problem with your database access -- maybe your utf-8 configuration is ineffective for some reason. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Managing Zope objects in Subversion
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Wildenhain wrote: Dieter Maurer wrote: When I remember right, Tres has a product that allows to dump and restore standard Zope objects to/from the file system. I forgot its name but you should be able to find it via your favorite search engine. I wonder if Tres has also finished DAV support of Zope to also support DeltaV - this would make Zope immediately a SVN server - problem solved :-) Well... wishfull thinking ;) Tres never even *started* adding Delta-V support, beyond reading the specification and speculating about how hard it would be. ;) Yes I know ;) Btw, how hard would it be? Provided to just use hysterical versions of objects (and forbid/disable packing)? Regards Tino ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope utf-8 problem using MySQL
Hugo Ramos wrote: Yellow ppl, I'm using Zope 2.10.5 + MySQL 5.0.51a + MySQL-python-1.2.2. Why? I mean, is there a special business reason to use MySQL? Just curious... T. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Managing Zope objects in Subversion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Wildenhain wrote: Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Wildenhain wrote: Dieter Maurer wrote: When I remember right, Tres has a product that allows to dump and restore standard Zope objects to/from the file system. I forgot its name but you should be able to find it via your favorite search engine. I wonder if Tres has also finished DAV support of Zope to also support DeltaV - this would make Zope immediately a SVN server - problem solved :-) Well... wishfull thinking ;) Tres never even *started* adding Delta-V support, beyond reading the specification and speculating about how hard it would be. ;) Yes I know ;) Btw, how hard would it be? Provided to just use hysterical versions of objects (and forbid/disable packing)? Im afraid that any special knowledge I had of that stuff has been swapped out of my brain for so long that you are in a much better position to answer your own question than I. 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 iD8DBQFH5BmT+gerLs4ltQ4RAhFmAKCvFYbmUWffbEi3QMmySrkaPFV1GQCg2CsQ 9zbam5DfEdim9hXCvdzG8LM= =qrIb -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope utf-8 problem using MySQL
yellow, I retrive the data using a Z MySQL Database Connection and the corresponding Z SQL Method. Everything works fine but the only way to get the utf-8 data is using SET NAMES 'utf-8' before the select statement. I wonder what is wrong... Is it possible to centralize this utf-8 setting in 1 place instead of using it on *EVERY* Z SQL Method??? Thanks Hugo On Fri, Mar 21, 2008 at 7:50 PM, Dieter Maurer [EMAIL PROTECTED] wrote: Hugo Ramos wrote at 2008-3-19 18:11 +: ... The problem is that when retrieving data from a table the international chars become alien symbols... How do you retrieve the data? You should check the data immediately when you receive it from the database. If it is already wrong at this place, you know there is a problem with your database access -- maybe your utf-8 configuration is ineffective for some reason. -- Dieter -- Hugo Ramos IT Project Manager http://www.hugoramos.eu/ [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope utf-8 problem using MySQL
yellow, It's a question of taste... I use a Macbook Pro/Leopard laptop instead of a PC/win32 laptop... Also a question of taste! :-) Thanks Hugo On Fri, Mar 21, 2008 at 8:23 PM, Tino Wildenhain [EMAIL PROTECTED] wrote: Hugo Ramos wrote: Yellow ppl, I'm using Zope 2.10.5 + MySQL 5.0.51a + MySQL-python-1.2.2. Why? I mean, is there a special business reason to use MySQL? Just curious... T. -- Hugo Ramos IT Project Manager http://www.hugoramos.eu/ [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
