August 2005 - Zope-Dev

Zope3 / ERP Project Launched
by Aurélien Calonne 31 Aug '05

31 Aug '05

Hi, On the behalf of ERP5 developer community,I am pleased to announce Zope3 / ERP Project and its new moto: "no overhead, high performance". The goal of the Z3ERP project is to leverage the Zope3 platform and build an ERP solution based on ERP5 technologies with the capability of handling more than 1,000 concurrent users or 1,000,000,000 business records and compete with the famous proprietary ERP solutions. The project has been discussed with ERP5 developers and customers in Africa, Americas, Asia and Europe for now one year. Initial high performance experimentations have been conducted with success and give us the confidence that this goal can be reached. Besides high performance, the project aims at providing full compatibility with Zope2 implementations of ERP5, developing Javascript Web user interfaces (AJAX) which increase enterprise productivity and are compatible with high latency WAN networks, creating predefined localisation guidelines and developing efficient model based configuration solutions. The project will be organised through a series of sprints and experience build-up sessions. Sprint activities are open to experienced ERP5 developers. Training sessions will be organised in parallel for experienced Zope developers who wish to gain ERP5 experience and participate in the next sprint. Project events will be published on www.z3erp.org. The first project sesssion will happen during the DZUG meeting on September 22 and 23 in Köthen/Anhalt city. Preferred licensing of project is GPL. Hosting of the project is on a dedicated Erp5.org workspace. Any contribution must be GPL compatible (ex. ZPL). Copyright is assigned to contributor on a per component level. To prevent any legal risks resulting from mergers or buyouts, all code will be formally licensed to the Foundation for a Free Information Infrastructure (FFII), a global independent software association. All project code must be archived in the FFII repository. Nexedi has already assigned 2 full-time engineers to this project. More information can be obtained by writing at z3erp(a)z3erp.org References http://www.z3erp.org http://www.erp5.org http://www.dzug.org/organisation/ http://www.ffii.org http://www.nexedi.com -- Aurélien Calonne - Tel. +33(0)6 62 05 76 14 Nexedi: Consulting and Development of Libre / Open Source Software http://www.nexedi.com ERP5: Libre/ Open Source ERP Software for small and medium companies http://www.erp5.org

1 0

medusa licence inconsistency
by Martin Kudlvasr 29 Aug '05

29 Aug '05

Hi, in Zope-2.7.7-final, there are two licences for ZServer/medusa: Zope-2.7.7-final/lib/python/ZServer/medusa/docs/README.html and Zope-2.7.7-final/lib/python/ZServer/medusa/dist/license.html Can someone please remove this inconsistency? By deleting one of these of clearing the situation otherwise. Thank you. -- Best Regards, Martin Kudlvasr Zope Portal Developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mkudlvasr(a)suse.cz Drahobejlova 27 tel: +420 296 542 382 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/

1 0

Puzzling change to guarded_getitem in Zope 2.8
by Richard Jones 27 Aug '05

27 Aug '05

I'm migrating our 2.7-developed Product to 2.8. The following change has me puzzled. In 2.7, AccessControl.ZopeGuards guarded_getitem has the following code: def guarded_getitem(object, index): [ snip handling of slices ] ... v = object[index] if Containers(type(object)) and Containers(type(v)): # Simple type. Short circuit. return v if getSecurityManager().validate(object, object, index, v): return v raise Unauthorized, 'unauthorized access to element %s' % `i` note the use of "index" in the validate call. In 2.8, this appears as: def guarded_getitem(object, index): [ snip handling of slices ] ... v = object[index] if Containers(type(object)) and Containers(type(v)): # Simple type. Short circuit. return v if getSecurityManager().validate(object, object, None, v): return v raise Unauthorized, 'unauthorized access to element %s' % `i` where "index" has become "None". This would appear to imply that we can't perform access controls on a per-item basis in sequences or mappings, unless we do so in the actual __getitem__ method, which implies there's no such thing as trusted code. We have an access policy implementation of: def _checkAccess(self, name, value): if name.startswith('CG'): return 1 if self.isValidAggregateName(name): return 1 return 0 security.setDefaultAccess(_checkAccess) which obviously doesn't work any more, since "name" is never a item name, it's always None. Richard

3 4

Create Zope 2.9 project wiki
by Fred Drake 26 Aug '05

26 Aug '05

I've created a project wiki for Zope 2.9: http://www.zope.org/Wikis/DevSite/Projects/Zope2.9/FrontPage The wiki is pretty bare at the moment. I've started adding some notes about moving the build and packaging support to use zpkg in the Tasks page: http://www.zope.org/Wikis/DevSite/Projects/Zope2.9/Tasks Feel free to start filling in other parts of the wiki as well. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> Zope Corporation

1 0

Build process for Zope 2.9
by Fred Drake 26 Aug '05

26 Aug '05

Hey all, I'm working on a revised build process for Zope 2.9, based on the work that we've done for Zope 3. What this means is that we'll have a setup.py that uses the code from zpkg (http://www.zope.org/Members/fdrake/zpkgtools/) to load metadata from the various packages are part of the checkout, and use distutils to perform the build. One thing that will need to change is the makefile that gets generated by the configure script. The current makefile has an enormous number of options that don't really seem to make sense, and many targets. I'd like to remove any that aren't being actively used, but it's hard to tell which those are. Would anyone object if we switch to something a lot closer to the Zope 3 makefile? There's basically in-place builds and tests, and that's it. Everything else is handled outside the makefile. Comments or objections? -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> Zope Corporation

3 3

3rd party product migrations
by Alan Milligan 26 Aug '05

26 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, We're now migrating our product stack to Zope2.8/Plone2.1 and have been considering how best to proceed with this. We have one overriding objective in that we're very interested in reducing the window between core releases and third party developers making new releases both now and into the future. To this end, we've set up a development channel, synonymous with Rawhide for those familiar with Redhat/Fedora release management practices. Using yum or up2date, you can access this channel at https://linux.last-bastion.net/RPC2/up2date/development to transparently upgrade to the latest core. We will be producing regular releases of things Zope and Plone into the future here. At this stage, you do need to create an account on the portal as you need to be Authenticated to download. The Zope2.8/Plone2.1 packages happily sit alongside older installations. If you're an author of anything on https://linux.last-bastion.net/RPC2/up2date/plope, we're particularly keen upon getting you involved. If you've a Plope product you'd like to get put on this channel, then please do feel free to contact us. We're hoping to grow the list of successfully migrated packages as quickly as possible. We of course realise that the Zope and Plone landscape is diverse, both in terms of finding source code, and operating system environments, but if you're even remotely interested in packaging, or have something to say, please feel free to subscribe to maintainers-subscribe(a)linux.last-bastion.net. Cheers, Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDDv8KCfroLk4EZpkRAkyUAJ92Ydp6nX+7uyoBQEv/+Qg96NceGQCgk7Dt nslcj7V7konlwbDMyAxYWU4= =glS5 -----END PGP SIGNATURE-----

1 0

coverage.py, profile and hotshot support in Zope's testrunner
by Stefane Fermigier 24 Aug '05

24 Aug '05

I have added support for coverage analysis using coverage.py from Gareth Rees and Ned Batchelder, as well as support for profiling using either the profile or hotshot modules from the Python standard library, to Zope 2's test runner test.py. Justification: - coverage.py will let you interactively focus on the modules you want to check for coverage. - profile is slow to collect data but quick for analysis. - hotshot is fast when collecting but very slow for analysis. On the other hand, one can feed the great KCacheGrind tool with hotshot data after some transformation and this is the best way I have found so far for interactively exploring profile data. Since I'm not a regular Zope commiter, I'd like to ask for comments and permission first before commiting. The test.py file is here: http://blogs.nuxeo.com/sections/blogs/fermigier/2005_08_21_coverage-py-prof… BTW: the patch is absolutely trivial (see attached file). S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! 1c1 < #!/home/fermigier/bin/python --- > #!/usr/bin/env python2.3 124,143d123 < --coverage < Use the coverage.py module from Gareth Rees < (http://www.nedbatchelder.com/code/modules/coverage.html) to collect data < for code coverage. This will output trace data in a file called < '.coverage'. You will need to call coverage.py after the test run to < analyse the data (-r for a line count report, -a for annotated file). < < --profile < Use the profile module from the standard library to collect profiling data. < This will output data in a file called '.profile'. You will need to use the < pstats module from the standard library after the test run to analyse the < data. < < --hotshot < Use the hotshot module from the standard library to collect profiling data. < This will output data in a file called '.hotshot'. You will need to use the < hotshot.pstats module from the standard library after the test run to < analyse the data. You may also use the hotshot2cg script from the < KCacheGrind sources to create data suitable for analysis by KCacheGrind. < 772,774d751 < COVERAGE = False < PROFILE = False < HOTSHOT = False 797,798c774 < "config-file=", "import-testing", < "coverage", "profile", "hotshot"]) --- > "config-file=", "import-testing"]) 850,855d825 < elif k == "--coverage": < COVERAGE = True < elif k == "--profile": < PROFILE = True < elif k == "--hotshot": < HOTSHOT = True 936,958d905 < < elif COVERAGE: < try: < from coverage import the_coverage < except: < print "You need to install coverage.py from " < print "http://www.nedbatchelder.com/code/modules/coverage.html" < sys.exit() < the_coverage.start() < main(module_filter, test_filter, libdir) < < elif PROFILE: < import profile < profile.runctx("main(module_filter, test_filter, libdir)", < globals=globals(), locals=vars(), < filename=".profile") < < elif HOTSHOT: < import hotshot < profile = hotshot.Profile(".hotshot") < profile.runctx("main(module_filter, test_filter, libdir)", < globals=globals(), locals=vars()) <

5 8

ZServer response RFC compliance improvement
by Jens Vagelpohl 23 Aug '05

23 Aug '05

Hi everyone, I'd like to get the zserver-content-length.patch createed by dunny in this collector issue: http://www.zope.org/Collectors/Zope/1866/collector_issue_contents merged into the Zope 2.7/2.8 branches and the trunk. It ensures that certain classes of responses (e.g. 304) correctly leave out the content-length header. Can anyone seee a valid reason for not merging it in? jens

3 3

Subtransaction backward compatibility
by Dieter Maurer 23 Aug '05

23 Aug '05

Subtransactions used to be used for two purposes: * ensure that newly created objects get "_p_" attributes (especially "_p_jar" and "_p_oid") * release memory in the mid of large transactions (i.e. reading and/or writing large amounts of objects) With ZODB 3.4, subtransactions are implemented as savepoints. They can still be used for the first purpose. But, they no longer start cache garbage collection. As a consequence, subtransactions/savepoints can be dropped at places where only the second purpose has mattered, e.g. in Zope's ZCatalog. -- Dieter

2 1

RE: [Zope-dev] Python 2.4 with zope 2.7.6, on Windows
by Aruna Kathiria 23 Aug '05

23 Aug '05

Yeah, it's true that I have to use Python 2.4 with Zope 2.7.6 Also I can't go for Zope 2.8.1. I also tried to fix few places but still cannot. Dieter, do you remember what and where you had to fix? Thanks.. With Regards, Aruna Kathiriya Sr.Consultant, CIGNEX Technologies, Inc T: 408.327.9900 x 306 F: 408.273.6785 E: aruna(a)cignex.com U: www.cignex.com "Implement IT Right" -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Monday, August 22, 2005 9:56 AM To: Aruna Kathiria Cc: zope-dev(a)zope.org Subject: Re: [Zope-dev] Python 2.4 with zope 2.7.6, on Windows Aruna Kathiria wrote at 2005-8-21 23:53 -0700: >Is it possible to use Python 2.4 with Zope 2.7.6 on windows plateform? We use Python 2.4 with Zope 2.7.2. However (!) I had to fix a few places (identified by failing test cases from Zope quite extensive test suite). Apparently, Zope 2.8.1 is better prepared for Python 2.4. And others already told you: you use Python 2.4 with Zope at your own risk! -- Dieter

2 1