April 2009 - Zope-Dev

Zope Tests: 8 OK
by Zope Tests Summarizer 23 Apr '09

23 Apr '09

Summary of messages to the zope-tests list. Period Wed Apr 22 12:00:00 2009 UTC to Thu Apr 23 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 22 20:50:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011531.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 22 20:52:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011532.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 22 20:54:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011533.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Apr 22 20:56:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011534.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Wed Apr 22 20:58:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011535.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 22 21:00:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011536.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Apr 22 21:02:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011537.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Wed Apr 22 21:04:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011538.html

1 0

Re: [Zope-dev] Request to mailing list Foundation-Info rejected
by Lacko Roman 23 Apr '09

23 Apr '09

Hi, Could someone explain me what that message means ? > -----Original Message----- > From: foundation-info-bounces(a)mail.zope.org [mailto:foundation-info- > bounces(a)mail.zope.org] > Sent: Wednesday, April 22, 2009 6:59 PM > To: Lacko Roman > Subject: Request to mailing list Foundation-Info rejected > > Your request to the Foundation-Info mailing list > > Posting of your message titled "Zope Committer Agreement" > > has been rejected by the list moderator. The moderator gave the > following reason for rejecting your request: > > "No reason given" > > Any questions or comments should be directed to the list administrator > at: > > foundation-info-owner(a)mail.zope.org I have have followed instructions at http://docs.zope.org/developer/becoming-a-contributor.html Thanks in advance Roman

2 1

zope.documentetemplate breaks with unicode
by Jens W. Klein 23 Apr '09

23 Apr '09

We're using zope.documenttemplate for ArchGenXML code generation. If we feed it with unicode-strings it breaks while joining its rendered parts, see http://zope3.pov.lt/trac/browser/zope.documenttemplate/trunk/ src/zope/documenttemplate/pdocumenttemplate.py#L335 I know, DTML is rarely used, but for code-generation its fine. Is this a bug or does DTML not support unicode? regards Jens -- Jens W. Klein - Klein & Partner KEG - BlueDynamics Alliance

2 1

People in the "Zope 3" and "ZMI" teams
by Martijn Faassen 22 Apr '09

22 Apr '09

Hi there, Just so we don't lose track of who are interested in maintaining Zope 3 (and/or the ZMI). I've distilled the following list of people who are interested in helping maintain Zope 3. This might mean making sure existing apps work, maintaining or replacing the ZMI, and working on making sure installation works. We can work out these details over time. I've sorted it all more or less in the order of perceived commitment, based on my statements and wild guesses on my part, I might be completely wrong. If you want to help, please reply to this thread and indicate your support. I'd suggest if you want to help you talk to the people nearer to the top of the list. But what typically works better is for the people on this list to tell zope-dev what they're doing, and how others could help them with particular bits, on a regular basis. Yusei TAHARA ------------ Concerning the ZMI: "For me, the ZMI is useful to managing local components, security settings, making views for ad hoc changes etc. I think it could be an optional package like grokui.admin. I'm interested in maintenance it." I'll note that Yusei is planning to start work on rearranging the ZMI into a smaller set of packages (by moving code into "zmi.core") soon. Please help him if you're interested! Fabio Tranchitella ------------------ "If the question was "who is interested in zope3, the application server, and willing to maintain it", I'd answer "me"." Concerning the ZMI: "We use the ZMI to manage applications, where applications are instances of a content object stored in the ZODB. All in all, we manage applications in a similar way we manage plone sites in zope2.x. If this specific feature is going to be removed, I'm willing to support and maintain it." Uli Fouquet ----------- On a UI for installation of apps, possibly to be shared inside the Zope Toolkit: "I'd be willing to help" He adds: "although I don't feel qualified enough to drive such a process." Stephan Richter --------------- "I have no problem keeping the Zope 3 KGS releases alive." Concerning the ZMI: "I have not used the ZMI since 2 years now and I am still considering myself writing Zope 3 apps." Concerning a documentation website for Zope 3: "I am not interested about that." Albertas Agejevas ----------------- "I'm very interested that existing applications that use the the zope.app server remain usable with future versions of Zope Toolkit libraries, or Zope 3 KGS if you will." He also adds: "I'm not interested in documentation or maintaining the installation story on any platform, that is attracting new users" Roger Ineichen -------------- "I'm willing to help to find a way to move the old code parts to a newer and better concept." Roger also says he's interested in maintaining the ZMI in some form or find something new to migrate to. "I will help to support such a Zope Toolkit management app which will allow to get rid of the zmi part." I'm not sure what he means with "the old code" He adds: "Note, I don't use this code in my own projects and I don't propose to do that just for fun. But if someone proposes to do it, I'm willing to help." Baiju M ------- "I am interested to maintain the packages necessary to create a simple application out of the box." He adds: "This is just an academic interest :)" Regards, Martijn

3 11

SVN Write access procedure
by Behrang Dadsetan 22 Apr '09

22 Apr '09

Hi! After 8-9 years of admiring Zope and using it now and then, I finally got myself to contribute to the grok project. I hope to contribute even more in the near and mid-term future. We seem to have an issue with the documentation for becoming an SVN Contributor. Here are the steps I followed and the dead-end I got to. Following diverse people's advice, I followed the instructions from http://www.zope.org/DevHome/Subversion/ImpatientPeoplesGuideToRequestingCom… which basically points to http://docs.zope.org/developer/becoming-a-contributor.html I filled out the form, scanned it and mailed the scan to foundation-info(a)zope.org as mentioned in the contact details of the foundation on the 18th of April. Shortly afterwards, I received an automated response: Subject: Your message to Foundation-Info awaits moderator approval [snip] The reason it is being held: Message body is too big: 1817623 bytes with a limit of 40 KB [snip] After this was a lengthy silence. So I followed the next step from becoming-a-contributor.html which says to nag Jim Fulton. The problem is Jim never heard of this process and never saw my initial request. He was suprised the DevHome/ImpatientPeopleGuide.. was modified. Any suggestions what the new process should be? Is the Zope foundation now responsible for giving SVN Write access now that the form is about sharing copyright with the Foundation? If so, who can one nag within the Zope Foundation? We need to update the documentation of this procedure once we figured it out :) Thanks! Ben.

4 3

Zope Tests: 8 OK
by Zope Tests Summarizer 22 Apr '09

22 Apr '09

Summary of messages to the zope-tests list. Period Tue Apr 21 12:00:00 2009 UTC to Wed Apr 22 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 21 20:45:33 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011523.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 21 20:47:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011524.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 21 20:49:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011525.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Apr 21 20:51:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011526.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Tue Apr 21 20:53:37 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011527.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 21 20:55:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011528.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Apr 21 20:57:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011529.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Tue Apr 21 20:59:40 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011530.html

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 21 Apr '09

21 Apr '09

Summary of messages to the zope-tests list. Period Mon Apr 20 12:00:00 2009 UTC to Tue Apr 21 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 20 20:47:03 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011515.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 20 20:49:04 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011516.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 20 20:51:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011517.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Apr 20 20:53:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011518.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon Apr 20 20:55:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011519.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 20 20:57:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011520.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon Apr 20 20:59:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011521.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon Apr 20 21:01:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011522.html

1 0

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 20 Apr '09

20 Apr '09

Summary of messages to the zope-tests list. Period Sun Apr 19 12:00:00 2009 UTC to Mon Apr 20 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=8) : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 19 20:55:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011512.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 19 20:44:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011507.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 19 20:46:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011508.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 19 20:48:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011509.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Apr 19 20:51:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011510.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sun Apr 19 20:53:02 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011511.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun Apr 19 20:57:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011513.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sun Apr 19 20:59:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011514.html

3 2

[Zope 2.12.0a2]Acquisition+ExtensionClass failures with Python 2.6.2/Linux
by Andreas Jung 20 Apr '09

20 Apr '09

Hi, I am working on the 2.12.0a2 release. I get test failures on my Linux box (OpenSuse 10.3/64 bit, fresh Python 2.6.2 installation): ---------------------------------------------------------------------- File "/home/ajung/.buildout/eggs/Acquisition-2.12.1-py2.6-linux-x86_64.egg/Acquisition/tests.py", line 1732, in Acquisition.tests.test_proxying Failed example: list(i.c) Exception raised: Traceback (most recent call last): File "/home/ajung/.buildout/eggs/zope.testing-3.7.1-py2.6.egg/zope/testing/doctest.py", line 1356, in __run compileflags, 1) in test.globs File "<doctest Acquisition.tests.test_proxying[11]>", line 1, in <module> list(i.c) MemoryError ---------------------------------------------------------------------- File "/home/ajung/.buildout/eggs/Acquisition-2.12.1-py2.6-linux-x86_64.egg/Acquisition/tests.py", line 1781, in Acquisition.tests.test_proxying Failed example: list(i.c) Exception raised: Traceback (most recent call last): File "/home/ajung/.buildout/eggs/zope.testing-3.7.1-py2.6.egg/zope/testing/doctest.py", line 1356, in __run compileflags, 1) in test.globs File "<doctest Acquisition.tests.test_proxying[23]>", line 1, in <module> list(i.c) MemoryError ---------------------------------------------------------------------- File "/home/ajung/.buildout/eggs/ExtensionClass-2.11.1-py2.6-linux-x86_64.egg/ExtensionClass/tests.py", line 419, in ExtensionClass.tests.test_pickling_w_slots_w_empty_dict Failed example: pickle.loads(pickle.dumps(x, 0)) == x Expected: 1 Got: False ---------------------------------------------------------------------- File "/home/ajung/.buildout/eggs/ExtensionClass-2.11.1-py2.6-linux-x86_64.egg/ExtensionClass/tests.py", line 421, in ExtensionClass.tests.test_pickling_w_slots_w_empty_dict Failed example: pickle.loads(pickle.dumps(x, 1)) == x Expected: 1 Got: False ---------------------------------------------------------------------- File "/home/ajung/.buildout/eggs/ExtensionClass-2.11.1-py2.6-linux-x86_64.egg/ExtensionClass/tests.py", line 423, in ExtensionClass.tests.test_pickling_w_slots_w_empty_dict Failed example: pickle.loads(pickle.dumps(x, 2)) == x Expected: 1 Got: False However I have no failures on MacOSX. WTF? Andreas

3 4

Best way to invoke paster/WSGI apps on cmdline
by Uli Fouquet 19 Apr '09

19 Apr '09

Hi there, As Grok is now approaching the 1.0 release we (i.e. some Grok developers and me) want to have a 'compliant' way to offer paster-based serving of Grok instances. This means mainly that when a user creates a project with `grokproject`, we want to have the config files (deploy.ini, zope.conf, etc.) generated in a location, that users expect. Some 'standard' location if such a thing should exist. This also applies to the name/functionality of the script to start the paster server. Currently we do it like this with `grokproject`: Configuration files (deploy.ini, debug.ini, zope.conf, site.zcml, zdaemon.conf) are generated by zc.buildout in a local parts/etc/ directory from templates in a project-local etc/ directory. Furthermore we let buildout create a script ``bin/paster``, so that you can start your instance with:: $ bin/paster serve parts/etc/deploy.ini Nobody seems to like this (including myself, although I am mainly to blame for that). Especially the parts/etc/deploy.ini path is too 'hidden'. Time to learn from others. Other frameworks (repoze.bfg, TurboGears for example) do it differently and it looks like there is also the z3c.recipe.paster-way to do it, as Roger Ineichen stated yesterday on this list. Here's a short (probably incomplete) list of some 'full-stack' paster-capable 'frameworks' and how they invoke paster from the commandline (please correct/extend if I am wrong/incomplete here): ================ =================== ============================ Framework Ini-file location Paster call ================ =================== ============================ grokproject parts/etc/ bin/paster serve \ parts/etc/deploy.ini repoze.bfg <project root> paster serve MyProject.ini turbogears2 <project root> paster serve development.ini pylons <project root> paster serve development.ini zopeproject etc/ bin/paster serve \ etc/deploy.ini z3c.r.paster parts/<app>/ bin/app So we have two things to decide: (1) how do we want to let people invoke paster and (2) where do we generate the ini-files? I guess there are pros and cons for every of the approaches and we already discussed some of them in the Grok community, but the most important thing is, that we would like to keep Grok compatible with other frameworks/approaches, so that people feel a bit more used to it when they try it for the first time. Collected (incomplete) cons: - grokproject: hidden ini-file path, complicate paster invoke - zopeproject: supports only relative paths, one cannot invoke /abs/path/to/project/bin/paster serve ... from outside the project dir - z3c.recipe.paster: not sure whether commandline args like ``--reload`` are respected; invocation is different from other paster-based frameworks (this approach, however, looks most attractive to me). - turbogears2/pylons: not buildout based by default; makes it harder to create collaborative SVN-based projects. At least it would be nice to have a common approach or 'best practice' recommendation when it comes to Zope based paste deploys. It would be even nicer to have an approach that is similar also to non-Zope environments. We'd like to follow such a convention with `grokproject` and learn from other's expericences in that matter. Best regards, -- Uli

4 6