September 2002 - Zope-Dev

Future of StructuredText
by Andreas Jung 05 Sep '02

05 Sep '02

The exisiting implementation of StructuredText in Zope has several disadvantages: - its behaviour depends on the locale settings (letters and punctuation is taken from the locale settings). In some case the locale settings are imcomplete (characters ¡ and ¿ are not available through the locales as puncuation characters). - the behaviour of STX is not very well defined (what are allowed letters, what are allowed punctuation characters...) With the upcoming importance of reStructuredText (PEP 12) there is a real need for a better StructuredText implementation for Zope. reStructuredText solves these problems by using a reasonable specification and by avoiding ambiguities. RIchard Jones also implemented a first version of a reStructuredDocument product. I would be fine to have reStructuredText inside the Zope core (for 2.7) and to deprecate the current StructuredText in the long run. Open points: how to migrate exisiting STX documents to reStructuredText Cheers, Andreas --------------------------------------------------------------------- - Andreas Jung http://www.andreas-jung.com - - EMail: andreas at andreas-jung.com - - "Life is too short to (re)write parsers" - ---------------------------------------------------------------------

9 12

SWAP issue
by Ahsan Imam 05 Sep '02

05 Sep '02

Hello All, I am currently running zope 2.5 and python 2.1.3. The machine has 2 gigs of rams and is running on Red Hat 7.2. After starting zope eveything works fine for a while. Slowly the swap starts to swell up and after a few hours the machine has to be rebooted. The funny thing is that free shows that there is almost a gig of RAM free and swap keeps on growing. After a while the machine simply hangs. I have recompiled python and zope. Turned on profiling. I have looked through the stupid.log. There are no core dumps either. I have also tried running zope with one thread. Does anyone have suggestions. Thanks

3 2

Improving product management
by Jeffrey Chan 05 Sep '02

05 Sep '02

I'm sure this has been proposed a thousand times b4. Product management/download/installation really should be integrated into ZMI, kinda like what apt-get does now. All products is already sitting on a central repository (zope.org) all that's needed is a front-end and a standard packaging policy. There's probably good reason that there's still no TTW product management in Zope (complexity, I assume). But how about switching Zope's Python runtime to ActiveState distro? ActiveState already has PyPPM for package management, why not customize it for Zope? Create an additional ZopePPM that queries the zope.org repository for packages, while leaving PyPPM for installing Python runtime libraries. Ideally, if u use ZopePPM to install something like MySQLDA, it'll resolve the dependancies and invoke PyPPM automatically to install addtional Python runtime libraries in the correct locations. No more Python runtime lirary installation hell!! Just a thought. How u guys would consider the possibility. pz. -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup

4 5

Speaking of Structured Annoyances
by Jeffrey P Shell 05 Sep '02

05 Sep '02

Um, how does one escape * in STX-NG? As in - what if one is entering an equation inline like 2 * 2 * 3 = 12? Or, does one just fall back on using x? -- Jeffrey P Shell www.cuemedia.com

4 5

Re: Future of StructuredText
by David Goodger 05 Sep '02

05 Sep '02

Simon Michael wrote: >>> My two cents - there are some things in rST I would like to have but I >>> think it has gone too far with it's rules. Richard Jones wrote: >> This seems to be a common argument, and I honestly can't understand it. I'm >> not going argue it here, I'll just point you all to the "primer" document >> which outlines the basics of ReST: >> >> http://docutils.sourceforge.net/docs/rst/quickstart.html > > Hi Richard, > > It was more an expression of personal taste than an argument. But I > didn't understand your not understanding, I believe Richard is referring to a phenomenon I've experienced as well (although it's probably not what Simon initially complained about, which was in fact the *PEP* rules). Newbies will read through the reStructuredText spec and gasp, "Too many details! Too many rules! Too complex!", followed by, "Not for me!". Thanks to Richard, we now have the Primer document referenced above. I've just added a note to the beginning of the spec, basically saying "New Users: read the Primer first!" There are also the people who complain that reStructuredText is "too complex", referring to the number of constructs available. It's not complex; it's rich. To the new user, the constructs listed in the Primer above are sufficient. But when the user has need for more sophisticated constructs, they're ready & waiting. Other markups, like StructuredText, are much more limited; they reveal their limitations when the user needs more than a really simple "toy" markup. reStructuredText aims for a higher level of completeness and flexibility. Of course, there are limits inherent in the premise of readable plaintext, and there are applications for which these limits rule out the use of reStructuredText. But reStructuredText pushes the envelope, allowing for a lot more without resorting to verbose, ugly, unreadable XML-type markup. -- David Goodger <goodger(a)users.sourceforge.net> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/

1 0

Re: Future of StructuredText
by Simon Michael 05 Sep '02

05 Sep '02

Simon Michael <simon(a)joyful.com> writes: > The doc I read listed a large number of rules, including many that seemed > to want to exert more control over my text than they should. (I had a I tracked it down - it was the example rST PEP posted in comp.lang.python. So that would explain it. I read stuff like the below as being part of rST, when presumably they are a PEP thing. I don't think rST is the best of all possible markups (yet), but it's better than I might have suggested yesterday. -Simon ---------------------------------------------------------------------- (example rST PEP): "You must adhere to the Emacs convention of adding two spaces at the end of every sentence. You should fill your paragraphs to column 70, but under no circumstances should your lines extend past column 79. If your code samples spill over column 79, you should rewrite them. ... Tab characters must never appear in the document at all. A PEP should include the standard Emacs stanza included by example at the bottom of this PEP. ... PEP headings must begin in column zero and the initial letter of each word must be capitalized as in book titles. Acronyms should be in all capitals. ... You shouldn't have more than five levels of sections in your PEP. If you do, you should consider rewriting it. ... You must use two blank lines between the last line of a section's body and the next section heading. If a subsection heading immediately follows a section heading, a single blank line in-between is sufficient."

2 1

Confera and Zope 2.5.1
by Phil Langton 04 Sep '02

04 Sep '02

Does anyone know if the confera product will run under 2.5.1, tried with an old installation of 2.2.1 and it refuses to be anything but broken? I know there are other and better bulletin boards but need to keep some Confera sites running if possible. Any help/advice gratefully accepted. Phil =============================================================== Phil Langton (Senior Lecturer) Dept. Physiology, School of Medical Sciences, University of Bristol, Bristol BS8 1TD Tel: 44 (117) 928-9142; Fax: 44 (117) 928-8923 http://www.bris.ac.uk/Depts/Physiology/Staff/PDL/web_pdl.htm ===============================================================

1 0

What does error code 136 mean?
by Peter Keller 04 Sep '02

04 Sep '02

Hi, I am having trouble with the current version of ZWiki. ZWiki's author is puzzled, and suggested that I try one of the Zope lists. I set up a ZCatalog on a ZWiki folder as described at http://zwiki.org/HowToInstallAZwikiCatalog The following DTML from ZWiki's RecentChanges: <dtml-in Catalog sort=lastEditTime reverse> causes a python core file to be produced, and with stupid log enabled I get this message: 2002-09-02T09:57:30 ERROR(200) zdaemon zdaemon: Mon Sep 2 10:57:30 2002: Aiieee! 322190 exited with error code: 136 I am using Zope 2.5.1 with python 2.1.3 under HP (was Compaq) Tru64 Unix version 5.0 Does anyone have any suggestions about what is going wrong? Thanks, Peter. -- ======================================================================== Peter Keller. | "Research without indebtedness is European Bioinformatics Institute,| suspect, and somebody must always, Hinxton Hall, | somehow, be thanked." Cambridge, CB10 1SD, UK | --- Umberto Eco ----------------------------------- Email: keller(a)ebi.ac.uk | Tel. (+44/0)1223 494637 | Macromolecular Structure Database Fax. (+44/0)1223 494468 | http://msd.ebi.ac.uk ========================================================================

3 3

[ANNOUNCE] emacs html helper mode with dtml support
by de ZORZI Frederic 04 Sep '02

04 Sep '02

http://www.zope.org/Members/fredz/html-helper-mode Here you can find a modified version of html-helper-mode.el (3.0.4jolly) for emacs who supports dtml tags : - Auto-indentation (with a little help :)) - Shortcuts / Completion - Tag regions I'd be pleased to receive feedback Fredz.

2 1

Fw: [Zope] xmlrpc redirect response
by Casey Duncan 03 Sep '02

03 Sep '02

What do you all think of this? Do redirects ever make sense to an xml-rpc call? In reading the spec it says (in reference to the response status value): "Unless there's a lower-level error, always return 200 OK." Now granted this problem stems from calling a ZMI API through xml-rpc, but for better or for worse, that is the de-facto TTW API into Zope. And since you can't help passing REQUEST and RESPONSE in, you can't stop the redirect by omitting the R/R arguments through xml-rpc. Thoughts anyone? -Casey ----- Original Message ----- From: "Marco Aurelio Catunda Martins" <catunda(a)embratel.net.br> To: <zope(a)zope.org> Sent: Saturday, August 31, 2002 5:55 PM Subject: [Zope] xmlrpc redirect response > Hello, > > When I try to adding an DTML Document by xmlrpc call the following > error appear: > > xmlrpclib.ProtocolError: <ProtocolError for localhost:8080/RPC2: 302 Moved > Temporarily> > > The 302 error code is about redirect response. I think there is no make > sense redirect in xmlrpc call, so change zope source. I put the following > method at Response class in xmlrpc.py file: > > def redirect(self, location, status=302, lock=0): > pass > > What do you think about it? Is there any problem? > > -- > Marco Catunda > > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://lists.zope.org/mailman/listinfo/zope > ** No cross posts or HTML encoding! ** > (Related lists - > http://lists.zope.org/mailman/listinfo/zope-announce > http://lists.zope.org/mailman/listinfo/zope-dev ) >

3 4