- Zope-Dev - Zope lists

Zope Tests: 5 OK
by Zope Tests Summarizer 28 Apr '08

28 Apr '08

Summary of messages to the zope-tests list. Period Sun Apr 27 11:00:00 2008 UTC to Mon Apr 28 11: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: Sun Apr 27 21:00:55 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009470.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun Apr 27 21:02:26 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009471.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun Apr 27 21:03:56 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009472.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun Apr 27 21:05:26 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009473.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun Apr 27 21:06:56 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009474.html

1 0

Zope2 interfaces delenda est!
by Tres Seaver 28 Apr '08

28 Apr '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to rip out the old Interface module from the 2.11 branch and the trunk, along with all the useless decoys which import it. THere is no *good* BBB reason to keep them around: anybody still depending on them in A.G. 2008 needs to switch over, anyway. Objections? I'll fix the CMF breakage myself, but the Plone folks are going to have to revisit lots of grotty bits. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIEie++gerLs4ltQ4RAsuxAKCC74aUHZzJwblAWEAyvvhu4S55AwCgpuwZ xSuzLdUKg/zi2uPFeFdMOB0= =qZSC -----END PGP SIGNATURE-----

7 9

ZopeVocabularyRegistry
by yuppie 27 Apr '08

27 Apr '08

Hi! ZopeVocabularyRegistry allows to register vocabularies as utilities. _clear() in zope.app.schema.vocabulary hooks it up, importing zope.app.schema touches zope.app.schema.vocabulary and triggers the '_clear' call. Zope 2.10 did hook up ZopeVocabularyRegistry as a side effect of loading the deprecated vocabulary directive. http://svn.zope.org/?view=rev&rev=77097 removed the deprecated directive, breaking vocabulary registration. What is the recommended way to hook up ZopeVocabularyRegistry? Importing zope.app.schema.vocabulary in Five's __init__.py? Cheers, Yuppie

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 27 Apr '08

27 Apr '08

Summary of messages to the zope-tests list. Period Sat Apr 26 11:00:00 2008 UTC to Sun Apr 27 11: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: Sat Apr 26 21:09:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009465.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Apr 26 21:11:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009466.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat Apr 26 21:12:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009467.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Apr 26 21:14:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009468.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Apr 26 21:15:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009469.html

1 0

Proposal: Deprecate GlobalTranslationService and FiveTranslationService
by Hanno Schlichting 26 Apr '08

26 Apr '08

Hi. I'd like to propose to deprecate the Products.PageTemplates.GlobalTranslationService module and all custom translation handling from Products.Five. Rationale: In order to bring zope.i18n translation handling to the masses, some backwards compatibility code for PlacelessTranslationService and Localizer has been added to Five. Nowadays PlacelessTranslationService trunk doesn't need any of this BBB support anymore and everyone else has switched to using direct zope.i18n translations, making the BBB code unnecessary. This will remove another difference in the Zope2 PageTemplates Expression context moving them closer to the zope.tales implementation. Implementation: Deprecation warnings will be added and the code marked for deletion in two releases with a minimum of a 12 month timespan. Opinions, comments? Hanno

1 0

Proposal: Merge philikon-aq branch into Zope trunk
by Hanno Schlichting 26 Apr '08

26 Apr '08

Hi. I'd like to propose to merge the philikon-aq branch into Zope trunk aka Zope 2.12. Scope: For those unfamiliar with the branch, it makes Acquisition aware of __parent__ pointers. This makes it unnecessary to use Acquisition mixin's for Zope 3 code to use them in Zope 2 code. The security machinery of Zope 2 will still be able to work as expected. Status: All tests in the Zope itself pass. New tests have been written for all edge cases found during the development of the branch. As a real world exposure Plone has been used to test the branch. All tests in Plone except one edge-case of a monkey-patch loaded package still pass. Plone in current versions make heavy use of Zope 3 and Five technologies inside Zope 2, so I see this as a very good indicator for the readiness of the branch. The one edge-case is something which needs to be fixed in Plone, as it doesn't make use of any official API. Risks: Using Zope 3 code inside Zope 2 has lead to various 'inventive solutions' to work around problems. Some of these have not used official API's. It is possible that some of those might need to be adjusted. Adjusting them should be straight forward in most cases and mostly consist of removing the hackish workarounds. The second problem that might arise, is that the implicit assumption that every object inside Zope 2 inherits from Acquisition base classes no longer holds. Code that relies on the various aq_* attributes to be there need to be adjusted to use the Acquisition methods instead. This change is trivial to do and doesn't need to be done at first. It only needs to be done when you want to allow direct Zope 3 code in your application. As part of the branch all code in Zope 2 itself have been adjusted to use the aq_* methods. Timeline: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? Hanno P.S. Thanks to philiKON for doing most of the work on this branch :)

13 26

new zope.org, sphinx, and documentation management
by Paul Carduner 26 Apr '08

26 Apr '08

Hi All, <lots of small talk follows, scroll down to **** section for the main point of this email> I guess I have officially volunteered to write content for the new zope.org site in the zope 3 section. Part of that involves describing what zope 3 is in a concise manner. I realize there are probably a lot of different opinions about what zope 3 is, so I would like to solicit the community to provide me with some ideas of what zope 3 is to you. It doesn't have to be anything fancy or publishable, just a bulleted list of "what zope 3 means to me" would be fine. I will aggregate these ideas and try to present it in an easy to read form. I don't want to start any arguments about what zope 3, so let's wait until I have something written before we start arguing :). Besides giving the 10000 foot view of zope 3, there is also a section for zope 3 documentation on the new site, which should probably include detailed developer documentation along with tutorials, howtos, references, etc. Fortunately, a little known fact is that there is already a fair amount of up-to-date documentation about many zope3 packages in the form of doctests (some better written for end-user consumption than others). Few people know about this because the documentation is not aggregated anywhere (except for some bits on apidoc.zope.org) You have to know to look on svn.zope.org or pypi pages to find the rest of it. Rather than writing a bunch of new documentation on the new zope.org site from scratch, I would like to harness the existing documentation, and just publish it in a nice way. To this end I have taken a look at sphinx, the new documentation publishing tool used by python.org. In short, it looks really good, and I think we could use it for zope documentation. Here is my thinking: Keeping *lots* of documentation maintained in any CMS or wiki style website is hard, because the people writing the code want to maintain everything (including documentation) in one place: subversion. It is too much to ask every developer to update a website every time they make a change to the codebase, because the website lives in firefox, while the code lives in vim or emacs. But if the documentation lives with the code, updating the documentation can become part of the normal flow of writing software (just like writing tests is part of the normal flow). So ideally, all package specific documentation *including tutorials and other end user docs* should live along side the code in subversion. Now the trick is just publishing this documentation. ***** THE POINT OF THIS EMAIL IS BELOW ***** I would like to develop a buildout recipe that generates aggregated documentation for a package (like z3c.form) using sphynx and publishes it to the new zope.org website. I want updating of zope documentation on zope.org to be as easy as uploading a package to pypi: When you are ready to make a release of a package, you would then do: $ cd z3c.form/tags/2.0/ $ python setup.py register sdist upload $ ./bin/buildout $ ./bin/update-documentation You would then be able to go to http://www.zope.org/projects/zope3/documentation/z3c.form and see everything from developer docs, to tutorials, to how-tos, etc. What do people think of this idea and who wants to help me implement it this weekend? -- Paul Carduner http://www.carduner.net

7 15

Zope Tests: 5 OK
by Zope Tests Summarizer 26 Apr '08

26 Apr '08

Summary of messages to the zope-tests list. Period Fri Apr 25 11:00:00 2008 UTC to Sat Apr 26 11: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: Fri Apr 25 21:01:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009460.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Apr 25 21:02:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009461.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Apr 25 21:04:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009462.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Apr 25 21:05:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009463.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Apr 25 21:07:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009464.html

1 0

comments on DateTime(DateTime()) preserving timezone? (launchpad 200007)
by Paul Winkler 26 Apr '08

26 Apr '08

I've got a fix, with tests, for https://bugs.launchpad.net/zope2/+bug/200007 checked in at Zope/branches/slinkp-datetime-200007 If nobody objects in the next few days, I'd like to merge this to trunk, and the 2.11, 2.10, and 2.9 branches. -- http://www.slinkp.com

2 1

ZConfig 2.5.1 test failures
by Timothy Selivanow 25 Apr '08

25 Apr '08

I'm getting a Traceback when running `python setup.py test` for ZConfig-2.5.1 as per the changelog. Attached is the output, let me know how I can help. I'm not a proficient python programmer; however, I'm more than willing to learn more. --Tim _________________________________________________________________ / They collapsed ... like nuns in the street ... they had no teen \ \ appeal! / ----------------------------------------------------------------- \ \ \ \ /\ ( ) .( o ).

4 7