February 2006 - Zope

Re: [Zope3-Users] Re: [Zope] Debugging doctests
by Chris McDonough 24 Feb '06

24 Feb '06

On Feb 23, 2006, at 1:57 PM, Benji York wrote: > > But it's of course a judgment call. > > Perhaps this is just one of those to-each-his-own things. <shrug> > My own are doctests. ;) Sure. I actually really appreciate reading good doctests, they help a lot, and they beat not having any docs at all any day! A non-sequitur: For truly standalone packages, I suspect that people expect some form of non-executable narrative documentation to be included that ties the continued use of the package together with its implementation. In my experience, it's easy to get lured into thinking that you've documented a package properly because it has doctests and interface documentation, when in reality it probably needs some other form of documentation beyond the doctests (e.g. high- level overview of purpose, how to install it, what other packages it depends upon, which versions of Python/Zope it works with, who is responsible for maintaining the package, where to report bugs, and so on). I suppose this is really a packaging issue, but it would be nice if more packages in the zope namespace package were treated as "islands" like this that could be installed separately from Zope proper. It would also likely help prevent inappropriate dependencies from creeping in. Zope 2 wasn't born a mess of spaghetti dependencies, they just sort of grew like weeds over time. - C

4 5

[ANN] Zope 2.9.1 released
by Andreas Jung 24 Feb '06

24 Feb '06

Hi all, on behalf of Zope Corporation and the Zope community I am pleased to announce the release of Zope 2.9.1. You can download it from http://www.zope.org/Products/Zope/2.9.1/ Some new features of Zope 2.9: - ZODB 3.6 - Five 1.2 - integration for Zope 3 events for object creation and deletion - Zope 3 i18n integration for page templates For more information on what is new in this release, see the CHANGES.txt files for the release: http://www.zope.org/Products/Zope/2.9.1/CHANGES.txt Please bring all the bugs you have found to the Zope bugtracker: "http://collector.zope.org/Zope":http://collector.zope.org/Zope For more information on the available Zope releases, guidance for selecting the right distribution and installation instructions, please see: http://www.plope.com/Books/2_7Edition/InstallingZope.stx Support Python versions: Zope 2.9 requires Python 2.4.2 (Python 2.4.1 is still acceptable). Older Python versions are no longer supported. Thanks to all being involved in this release. -- Andreas Jung (andreas at zopyx dot com)

1 0

Re: [Zope] attribute used to index PDFs?
by Garth B. 24 Feb '06

24 Feb '06

Hmm? I must have missed where it was suggested in this old thread to enter this "issue" into the bug tracker. At any rate, what I eventually concluded was that this really isn't an issue, just a misconception I had about what TXNG3 actually provides as native indexing support (given the appropriately installed converters). Assuming the user isn't using Plone or something else that provides a TXNG hook into the File's data, the user still needs to write the appropriate adapter to get the indexer to pull the raw data from the object to then be converted and indexed. This was a bit of a change from what I was used to with TXNG2 which does know how to pull the data from File objects. Since I didn't have enough time to research what was involved in writing an adapter, I fell back to using TXNG2. It worked well and accomplished what I needed. Garth On 2/24/06, Andreas Jung <lists(a)andreas-jung.com> wrote: > > > --On 12. Dezember 2005 14:54:09 -0500 "Garth B." <garthb(a)gmail.com> wrote: > > > On closer inspection, the Word docs aren't actually being indexed > > appropriately either. When I browse the vocabulary for these indexed > > Word docs, I happen to see textual content that can be seen by also > > cat'ing the document to the stdout. The vocab includes other strings > > that certainly are not content. I guess they're string > > representations of binary content. > > > > These are other things that I noticed, maybe they won't amount to > > anything: > > > > - When I watch the processes during indexing w/top I don't see wvWare > > or pdftotext appear. Maybe they won't. > > > > - I also inserted a couple of LOG.warn's in src/textindexng/content.py > > around line 130 ( if d.has_key('mimetype'): ), and this test always > > fails, thereby skipping conversion. > > > > - Digging further in this file, "mimetype" is only defined when > > extract_content() in content.py calls "icc.addBinary(...)". This only > > happens when the indexed object provides a txng_get() hook (or I > > suppose if an adapter exists). That whole block (around lines 81 - > > 93) never gets hit with my PDFs or Word docs during indexing. When I > > index a large number of PDFs I will get a number of TypeErrors raised > > around line 110 when extract_content() notices that the data isn't a > > [unicode] string. > > > > Is the standard Zope File object supposed to expose a txng_get hook? > > > > On 12/12/05, Garth B. <garthb(a)gmail.com> wrote: > >> Hi Andreas, > >> > >> Neither PrincipiaSearchSource nor SearchableText does anything for > >> these File-type objects. I guess nothing for SearchableText is > >> expected since these are not CMF or Plone-derived objects. The only > >> way I've managed to get *anything* indexed for these File-type objects > >> is by specifying the "data" attribute. > >> > >> A couple of related postings that I've found through a bit of Googling > >> have also noted having to use "data" when indexing these kinds of > >> files, for example: > >> http://mail.zope.org/pipermail/zope/2003-August/139702.html > >> > >> So, I should be able to use PrincipiaSearchSource? I've only used > >> that for text-oriented objects like Page Templates. I'll keep digging > >> around, but I welcome any suggestions for what the problem could be or > >> how I can debug this further. > > Maybe you should bring this to TXNG bugtracker (as suggested!). > > -aj

1 0

Re: [Zope3-Users] Re: [Zope] Debugging doctests
by Lennart Regebro 24 Feb '06

24 Feb '06

On 2/23/06, Gary Poster <gary(a)zope.com> wrote: > You effectively can't step through all the tests (with a single > pdb). You can step through a single line in the test well. While it > sounds limiting, that has proved quite sufficient for me in > practice. YMMV, of course. Sigh. doctests really do suck. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

4 6

Re: [Zope] attribute used to index PDFs?
by Andreas Jung 24 Feb '06

24 Feb '06

--On 12. Dezember 2005 14:54:09 -0500 "Garth B." <garthb(a)gmail.com> wrote: > On closer inspection, the Word docs aren't actually being indexed > appropriately either. When I browse the vocabulary for these indexed > Word docs, I happen to see textual content that can be seen by also > cat'ing the document to the stdout. The vocab includes other strings > that certainly are not content. I guess they're string > representations of binary content. > > These are other things that I noticed, maybe they won't amount to > anything: > > - When I watch the processes during indexing w/top I don't see wvWare > or pdftotext appear. Maybe they won't. > > - I also inserted a couple of LOG.warn's in src/textindexng/content.py > around line 130 ( if d.has_key('mimetype'): ), and this test always > fails, thereby skipping conversion. > > - Digging further in this file, "mimetype" is only defined when > extract_content() in content.py calls "icc.addBinary(...)". This only > happens when the indexed object provides a txng_get() hook (or I > suppose if an adapter exists). That whole block (around lines 81 - > 93) never gets hit with my PDFs or Word docs during indexing. When I > index a large number of PDFs I will get a number of TypeErrors raised > around line 110 when extract_content() notices that the data isn't a > [unicode] string. > > Is the standard Zope File object supposed to expose a txng_get hook? > > On 12/12/05, Garth B. <garthb(a)gmail.com> wrote: >> Hi Andreas, >> >> Neither PrincipiaSearchSource nor SearchableText does anything for >> these File-type objects. I guess nothing for SearchableText is >> expected since these are not CMF or Plone-derived objects. The only >> way I've managed to get *anything* indexed for these File-type objects >> is by specifying the "data" attribute. >> >> A couple of related postings that I've found through a bit of Googling >> have also noted having to use "data" when indexing these kinds of >> files, for example: >> http://mail.zope.org/pipermail/zope/2003-August/139702.html >> >> So, I should be able to use PrincipiaSearchSource? I've only used >> that for text-oriented objects like Page Templates. I'll keep digging >> around, but I welcome any suggestions for what the problem could be or >> how I can debug this further. Maybe you should bring this to TXNG bugtracker (as suggested!). -aj

1 0

Re: [Zope3-dev] The Zope Software Certification Program and Common Repository Proposal
by Stephan Richter 24 Feb '06

24 Feb '06

On Thursday 23 February 2006 20:29, Jim Fulton wrote: > This is quite a document and vision. I hope we can pull something > like it off. (Like many, I recognize the daunting size of the task.) I have already working parsers and writers for all file formats. I have also a preliminary (but tested) implementation of registering, managing, unregistering a package in the repository with the ZSCP. Kamal Gill has agreed to do some initial artwork for the site, which should be done mid-March. We will see how it proceeds. Roger suggested to maybe even do some of the work during the Swiss Eastern Spring. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training

1 0

Re: [Zope3-Users] Re: [Zope] Debugging doctests
by Chris McDonough 23 Feb '06

23 Feb '06

On Feb 23, 2006, at 1:17 PM, Benji York wrote: > Chris McDonough wrote: >> I dunno about sucking because they are quite good for >> documentation, but I tend to write plain-old unittests instead of >> doctests when I'm testing without any pretense towards writing >> documentation. If you test internals of a class in a doctest, >> the doctest body gets pretty cluttered, which tends to defeat the >> documentation-esque-ness of them. > > Are you talking about doctests in docstrings? If so, I definitely > see downsides to that use case. I was talking about doctests in > stand-alone text files. That's my (and several others) preferred > way of using them. Either. > > If you /were/ talking about stand-alone doctests, then I have no > idea what you're talking about. :) It's just opinion, but for example, I don't think zope/wfmc/xpdl.txt reads much better as a doctest than it would as a plain old unittest. But it's of course a judgment call. - C

1 0

RESOLUTION: Can Zope 2.9 Coexist With Zope 2.6 Using Different Ports?
by Mark, Jonathan (Integic) 23 Feb '06

23 Feb '06

Thanks for the help everyone. I needed to make the $Instance/var and $Instance/log directories readable and writable to the user that Zope 2.9 ran as. Once I did that the problem went away.

1 0

Python equivalent to Javascript "escape/unescape"
by Brian Sullivan 23 Feb '06

23 Feb '06

I was assuming that it would somehow be easy to do the equivalent to Javascript "escape/unescape" functions in a Python script but for some reason I just can't find out how to do it. Maybe I can't see the forest for the trees. Anybody out there have a cluestick to whack me with?

3 3

Debugging doctests
by Lennart Regebro 23 Feb '06

23 Feb '06

On 2/21/06, Stephan Richter <srichter(a)cosmos.phy.tufts.edu> wrote: > On Tuesday 21 February 2006 12:14, Lennart Regebro wrote: > > (btw, through all this, I assume that Jims fix for the doctest > > debugging problem that he mentioned did work, and that you now can > > insert an import pdb;pdb.set_trace() in the middle of the doctests. > > Right?) > > This has been fixed since ages. :-) Ah, not in Zope 2.9 it seems. Is this expected, or an I doing something wrong? I'm running the Five tests with bin/zopectl test --dir Products/Five as usual, and having a set_trace() in the doctests behaves exactly as with the old test runner, where you have to debug though the doctest running as well, which makes it pretty useless... Hang on, I just tried it with Zope 3.2 too, and it didn't work either. What am I doing wrong? -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

2 3