- Zope-Dev - Zope lists

Announce: FSPerlScript
by Alan Milligan 01 Nov '04

01 Nov '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This patch is against CMF-1.4.7, although one could equally argue it better suited elsewhere - there appear to me to be minor uncomfortable dependencies regardless of where it sits (unless it's made an independent product - which seems a little unwarranted given it's simplicity). This patch includes the following: ~ FSPerlScript.py ~ images/fspl.gif (needs an artiste to draw a padlock!) ~ tests/test_FSPerlScript.py ~ tests/fake_skins/fake_skin/test1.pl ~ tests/fake_skins/fake_skin/test2.pl ~ __init__.py (FSPerlScript registration) Unfortunately, FSPerlScript is not quite as useful as I'd anticipated, given that the 'use' statement is a restricted opcode. I am more than willing to discuss with any interested party(s) how we may implement a security mechanism whereby we can specify 'safe' Perl modules, much as we do with the Python modules_allow stuff. Cheers, Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBhLGxCfroLk4EZpkRAtr6AKDCvDnf1gglfN7xrCW/eEZu0bvOowCfb3Wc BkRbevjQM1X20IbvgC6kCFw= =yHdw -----END PGP SIGNATURE-----

2 1

Access to global methods in product creation forms
by Marco Bizzarri 29 Oct '04

29 Oct '04

Hi all. I would like to use a global method in the add form of a product. I've declared the method in the methods dictionary of the package. However, when I try to add the product, I receive an unauthorized exception. The environment is python2.3.4 and zope 2.7.3, running on Debian GNU/Linux. I've attached a simple test product showing the problem. Thanks you in advance for your support. Regards Marco

1 0

Re: [Zope-dev] Can I configure additional loggers via zope.conf?
by Ames Andreas (MPA/DF) 28 Oct '04

28 Oct '04

Hello, Fred Drake wrote: > Please file a feature request for this so we don't forget it. This > can be assigned to me, though I'm not sure when I'll be able to get > to it. Please look to http://zope.org/Collectors/Zope/1555. Unfortunately I don't know how to assign this to you. Thanks, andreas

1 0

Can I configure additional loggers via zope.conf?
by Ames Andreas (MPA/DF) 28 Oct '04

28 Oct '04

Hello, sorry if this the wrong list, I just wasn't sure. I'd like to use a python lib which creates and uses its own logger objects/hierarchy. This hierarchy is not a subtree of the 'event'-hierarchy or the other default Zope-logger hierarchies. Unfortunately I wasn't able to define a <logger> section in my zope.conf (without changing the Zope/Startup/zopeschema.xml). Given that the number of python libs using 'logging' seems to keep growing my question is: Is this my fault, a Zope bug, a wishlist item or a feature (I'm using 2.7.2 if that matters)? TIA, andreas

2 1

ZopeInterface
by Radoslaw Stachowiak 28 Oct '04

28 Oct '04

Hello, Could anyone please provide me information when ZopeInterface product is going to be updated ? And how is it related to zopex3 releases ? I'm gentoo linux (www.gentoo.org) developer maintaing all zope related packages, and we are considering inclusion of ZopeInterface as separate package (we already have zopex3_rc3). Thank You in advance. -- radek(a)gentoo.org

2 1

Guidelines for using Speedpack with Zope products
by cp.hennessy＠openapp.biz 28 Oct '04

28 Oct '04

Hi, I'm trying to improve the speed of a plone based site and have installed SpeedPack. However my understanding is that SpeedPack currently takes a conservative approach to a limited set of products. I would like to understand what limitations SpeedPack has and how I can extend it to be able to improve the speed of various products and methods which profilers seem to indicate are taking more time than I think they should. If anyone has experience of using SpeedPack I'd also appreciate any comments you may have. Also if this is the wrong list for this topic please tell me which is the correct list. Thanks CPH

2 1

RFC: Proposed backward-compatibility policy
by Jim Fulton 27 Oct '04

27 Oct '04

Below is a proposed policy on backward compatibility for Zope. Zope Policy on Backward Compatibility ===================================== Backward compatibility needs to be a very high priority. Clean software also needs to be a high priority. Unfortunately, these goals are often at odds. Providing backward compatibility support makes code more complex and, thus, less maintainable. Going forward, we will address these conflicting goals in the following ways; 1. During development, alpha testing, and beta testing of new releases, any backward-incompatible change will be considered a bug. That is, we will make all effort to make sure that each release of Zope is backward compatible with the previous two feature releases. 2. Backward compatibility support will be limited. When we make a change that would require a change in software or data, we'll add code to support the old software or data, but we will also add code to generate deprecation warnings when that support code is used. The deprecation warnings will say specifically when the backward-compatibility support will go away. This time will usually be expressed as a release number at least two feature releases past the next feature release. (For example, if the next feature release is release 3.1, then the backward compatibility support would not be removed any sooner than release 3.3.) In other words, we will limit the time extent of backward compatibility support, but we will give plenty of warning. When data changes are involved, we'll provide data conversion tools that will be available before we begin the deprecation process. An additional issue is that it is often difficult to figure out if subtle features are being used. (For example, a change in an exception base class might affect some client that expected to catch the exception based on it's base exception.) It is very hard for a developer to assess whether any applications are relying on a particular feature and thus whether backward-compatibility support needs to be provided. Often developers will make judgment calls. If they judge wrong, we need to catch this with testing. This leads to a 3rd point: 3. It is very important to catch backward compatibility problems during development of new releases. In particular, it is important to test new Zope releases before they are released in final form. If a backward-compatibility problem is found before the final release, it will be considered a bug and will be fixed (by adding backward compatibility support) if at all possible before the final release. After the final release, we may choose not to bother to fix backward-compatibility problems. Consumers of Zope have a right to backward compatibility, but they also have a responsibility to test Zope against their applications during the beta release cycle (or sooner) to make sure their applications work. Questions? Thoughts? Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

5 8

Reminder: Questioning among Zope developers
by Christian Theune 26 Oct '04

26 Oct '04

Hi, this is a short reminder, that the announced questioning is still running until 27th october. If you wanted to fill out the questionnaire, but didn't got to it yet, you still have two days left. Cheers, Christian Theune ---- Questioning about the Satisfaction of Software Developers within the Zope Community Dear Zope developers and users, I’m looking urgently for some more participants for my investigation about the satisfaction of active Zope Developers. As mentioned in my first Mail, the results of the investigation will be made available to the Zope Community. Thus, we hope that this study will contribute to improved collaboration within the Zope Community. The questionnaires will be treated anonymously. The completion of the questionnaire takes about 20 minutes. Please take part! Otherwise the results will not mirror everybody’s opinions. The questionnaire is available bilingually (English/German) at http://evaluation.gocept.comand should be filled out by the 27th of October the latest. For queries please contact Katrin Wodzicki via Katrin.Wodzicki@uni- jena.de In advance I thank you for your support! Regards, Katrin Wodzicki -- gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - ct(a)gocept.com - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development

1 0

Was: Re: 2.7.3 beta attribute permission problems
by Andreas Jung 25 Oct '04

25 Oct '04

Tres, how severe is the problem that you have fixed? According to some rumors the fix seems to break applications. The question for Zope 2.7.3 final is: is the problem severe enough to have it fixed for 2.7.3 with the risk of causing trouble with broken applications or can we defer the fix to Zope 2.8? Andreas

5 8

Proposed changes to the TAL specification
by Fred Drake 21 Oct '04

21 Oct '04

I'm proposing some (small) changes to the TAL specification. This would result in a new version of TAL for Zope X3 3.1 (and Zope 2.8 if anyone wants to backport the relevant code changes). The discussion will be on the ZPT list, where I've sent a copy of the proposal. The proposal is also located in the ZPT wiki at: http://zope.org/Wikis/DevSite/Projects/ZPT/RemoveInsaneConstructs If you're interested in these changes, please discuss them on the ZPT list. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> Zope Corporation

1 0